First, just a friendly reminder that there is a zodb-dev mailing list.
On this, check out Andrew Kuchling's page about ZEO development:
There's a section at the bottom with a brief discussion of
ConflictError, what it means, and how to handle it. Zope automatically
does the retry, but Python develops have to handle it themselves.
Here's a link with some information about what's known as application
level conflict resolution:
There's also some discussion at:
Hope this helps...
Cyril Elkaim wrote:
> We are testing ZODB directly from Python and have a multitread
> ConflictError problem.
> In short :-) if we open a connection in a first thread, then a second
> connection in a second thread and then commit the first one and then the
> second (the transactions are so interlaced)...
> Not only we have the ConflicError, even if obviously we do not modify
> or create the same objects. But in fact the last transaction doesn't
> even have its own objects saved.
> We are using ZODB from Zope 2.4. We have a similar problem using
> Berkeley Storage too (beta4).
> If the two threads are serialized eveything works fine (but that's no
> more multithreading no? ;-)
> So is it possible to access ZODB from a multithreaded application?
> Thanks in advance
> Cyril Elkaim
> Zope-Dev maillist - [EMAIL PROTECTED]
> ** No cross posts or HTML encoding! **
> (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce
> http://lists.zope.org/mailman/listinfo/zope )
Zope-Dev maillist - [EMAIL PROTECTED]
** No cross posts or HTML encoding! **
(Related lists -