Terry Kerr wrote:
portion of the state that was deamed to be in conflict. Shouldn't it be
returning the entire new state dictionary?
Dunno, I wonder if Mike can help, given he wrote the article?
Chris
___
Zope-Dev maillist - [EMAIL PROTECTED]
On Thu, 13 Sep 2001 09:40:43 +1000
Terry Kerr [EMAIL PROTECTED] wrote:
Chris,
I notice in the ZODB2 article that it states that the conflict
resolution method should return the state of the object after
resolving
the differences.. However, in the example the method only returns
the
Terry Kerr wrote:
I have a method which increments an attribute on the current object. I
have created a thread lock so that multiple threads accessing the method
simultaneously cannot stuff up the attribute value:
The ZODB doesn't work like that ;-)
As I understand it, each DB connection
Chris,
I notice in the ZODB2 article that it states that the conflict
resolution method should return the state of the object after resolving
the differences.. However, in the example the method only returns the
portion of the state that was deamed to be in conflict. Shouldn't it be
returning
Hi,
I have a method which increments an attribute on the current object. I
have created a thread lock so that multiple threads accessing the method
simultaneously cannot stuff up the attribute value:
lock = thread.allocate_lock()
def nextOrderNumber(self):
lock.acquire()
