Le lundi 30 août 2010 21:36:50, Jim Fulton a écrit :
I've mistakenly tended to view this situation as an edge case.
I confirm. I encountered similar problems when a given persistent object
defines a transformation to be applied to another object (or more simply, when
the presence/content of an
On Mon, Aug 30, 2010 at 5:36 PM, Jim Fulton j...@zope.com wrote:
...
This is a fairly serious problem. It's serious enough that I'm, going
to add some APIs in ZODB 3.10 to deal with it. One of these is:
class ReadVerifyingStorage(IStorage):
def checkCurrentSerialInTransaction(oid,
On Mon, Aug 30, 2010 at 6:39 PM, Shane Hathaway sh...@hathawaymix.org wrote:
On 08/30/2010 03:36 PM, Jim Fulton wrote:
The tricky thing about this is the last paragraph. If the method
doesn't raise an error, then there can't be updates to the object
until after the transaction commits. For
On 08/30/2010 03:36 PM, Jim Fulton wrote:
The tricky thing about this is the last paragraph. If the method
doesn't raise an error, then there can't be updates to the object
until after the transaction commits. For most current
implementations, this implies that the storage lock is help when
