23 Jan
2004
23 Jan
'04
2:56 p.m.
On Thu, Jan 22, 2004 at 11:26:23PM -0500, Jeremy Hylton wrote:
That right in a rough sense. ZODB uses optimistic concurrency control, so later transactions are aborted if they conflict with already-committed ones. But the transactions actually run concurrently.
Could you explain this a bit more? Because we run relatively high-write operations on our Zope/ZEO setup, we hit ConflictErrors quite a bit. I'd like to understand the underlying machinery here, ideally so I can come up with a fix. srl -- Shane Landrum, Software Engineer srl@boston.com boston.com / NY Times Digital