Bug 7196 [1] has forced us to consider deferring item deletes in all views as
was first mentioned last April [2]. Given the impact this is going to have on
the application, Bryan, Grant, Jeffrey, John, Morgen and I just met to discuss
how to implement this in a way that minimize disruption in the application.
For more background about the problem deferring delete is solving see [3].
The next step is for the repository to ensure that a defer-deleted item is not
going to be considered a member of any abtract set-based collection.
If this works well, trying to clear all bi-directional references this item
holds would be the follow-on step but it is unclear at the moment whether this
can be made safe.
To be continued....
Andi..
[1] https://bugzilla.osafoundation.org/show_bug.cgi?id=7196
[2] http://lists.osafoundation.org/pipermail/chandler-dev/2006-April/005840.html
[3] http://lists.osafoundation.org/pipermail/chandler-dev/2006-April/005837.html
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
