4 Jun
2007
4 Jun
'07
11:18 a.m.
On 5/31/07, Joachim Schmitz <js@aixtraware.de> wrote:
Hi,
I was able to locate the places in the Zope-sources where the conflict error is triggered. On my local system it's in
ZODB.FileStorage in the store-method there is
if serial != cached_tid: rdata = self.tryToResolveConflict(oid, cached_tid,serial, data)
in the tryToResolveConflict method of ZODB.ConnflictResolution there is:
committed = state(self, oid, committedSerial, prfactory, committedData) print "resolve", resolve resolved = resolve(old, committed, newstate)
I'm not really sure, but have a look here: http://mail.zope.org/pipermail/zope-dev/2006-June/027573.html http://mail.zope.org/pipermail/zope-dev/2006-June/027583.html Maybe that helps. -- Markus