>> ...
>> The short course in ZODB is that, when MVCC is in effect, a
>> read will return the state of the object as of the time the current
>> transaction began, even if the object has subsequently been
>> modified by some other transaction.

[Dieter Maurer]
> Whoever wants to use it right now: the "no more ReadConflictErrors"
> patch on
>   <http://www.dieter.handshake.de/pyprojects/zope>
> does precisely this (for storages that support history information).

How has that been working out for people (not limited to Dieter)?  That's
indeed what we're after, although Jeremy has in mind deeper/broader changes
aimed at being more efficient than digging thru history.

Zope-Dev maillist  -  [EMAIL PROTECTED]
**  No cross posts or HTML encoding!  **
(Related lists - 
 http://mail.zope.org/mailman/listinfo/zope )

Reply via email to