Community
Participate
Working Groups
Sticky views are broken in 2 ways: 1. The mechanism that excludes objects that were committed by the sticky session, from stickiness, works on a per-transaction basis, while it should work on a per-session basis. Result is that currently, a view can't find an objects that was newly committed by a transaction in the same session. 2. The sticky-or-not decision logic does not take into account that the view requesting the revision might be an audit view; and so audit-view behavior has been broken since the introduction of sticky behavior. Will provide testcases and patch shortly.
Created attachment 182952 [details] Patch This patch moves much of the sticky logic from the view/tx to the session, where it belongs (since stickiness is a session property), and in addition it properly excludes audit view from sticky behavior.
Created attachment 183074 [details] Patch v2 - ready to be committed Just reformatted slightly.
Committed to HEAD
Available in R20110608-1407