>> ZODB.POSException.ConflictError: database conflict error (
>> serial this txn started with 0x035b25f36751f988 2005-02-10 18:59:24.215675,
>> serial currently committed 0x035b743c6d186822 2005-02-24 17:00:25.569220)
[Dieter Maurer]
> Where is the "oid" in this "ConflictError" report?
> It is vital information to analyse which object causes the problem...
I don't know. I reformatted Paul's traceback to line up the timestamps
for easier reading, but there was no oid in the original either.
There wouldn't be, either, if no oid was passed to the ConflictError
constructor. ConflictError.__str__ only includes info for the stuff
it was told about:
def __str__(self):
extras = []
if self.oid:
extras.append("oid %s" % oid_repr(self.oid))
if self.class_name:
extras.append("class %s" % self.class_name)
if self.serials:
current, old = self.serials
extras.append("serial this txn started with %s" %
readable_tid_repr(old))
extras.append("serial currently committed %s" %
readable_tid_repr(current))
if extras:
return "%s (%s)" % (self.message, ", ".join(extras))
else:
return self.message
In Paul's case, the ConflictError occurred on the ZEO server, but the
traceback came from the ZEO client (just raising the Exception object
the ZEO server passed to it). There's no way then to guess what the
traceback might have looked like on the ZEO server side (boooo!).
Perhaps looking at the ZEO server log would have helped.
_______________________________________________
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 )
