On 5/31/07, Joachim Schmitz <[EMAIL PROTECTED]> 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
_______________________________________________
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
