OK, I retract my suggestion about reindexingDeferred(). Any objections
to my suggestion about observersDeferred()?
Andi Vajda wrote:
On Thu, 22 Mar 2007, Grant Baillie wrote:
Well, I don't know the details of what filters/monitors/indexes/etc
are coming in to play, but the attached test case raises a
LookupError: Access to skiplist is denied, it is marked INVALID
as written, and runs successfully if I remove the "with
self.view.reindexingDeferred():" statement. Since the raise is
triggered by a single attribute assignment (admittedly,
EventStamp.rruleset, which results in a boatload of recurrence and
triage status bookkeeping), I'm a little wary of adding
view.reindexingDeferred() to the proposed __setup__.
Like I said, the issue is not with the filter monitors but with the
boatload of user code running and causing access to indexes currently
invalidated. This issue is very valid and warrants caution but, and
this is my point, it is not a special case specific to filter monitors.
Andi..
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
