Re: conflict resolution for PersistentList

On Tue, 2004-05-25 at 17:37, Diez Roggisch wrote:
> > But you still shouldn't have seen *inconsistent* data.  That's another
> > mystery here.
> 
> I don't have inconsistent data - its just that the thread that committed 
> first 
> has the list of childs written, while the second ones data is lost. First 
> that went unnoticed due to the broken exception handling. 

It's good you were able to work around this, but it still shouldn't
happen.  Your data actually *is* inconsistent, given the constraints
that later versions of ZODB places on commits after a read conflict is
raised, even if it is caught later.  I'm paranoid because I have an
application that would break badly if this constraint wasn't met and I
want to make sure that indeed you are using a version of ZODB that was
known to have this bug.  So when you send your code, could you also tell
us which version of ZODB you're using and confirm that it does or does
not have the test method that Tim and Jeremy confirmed to be a good
indicator about whether the "prevent commit after read conflict"
behavior is present?

Thanks!

- C



_______________________________________________
For more information about ZODB, see the ZODB Wiki:
http://www.zope.org/Wikis/ZODB/

ZODB-Dev mailing list  -  ZODB-Dev@xxxxxxxx
http://mail.zope.org/mailman/listinfo/zodb-dev