> Not correct. _p_resolveConflict is used in Zope 2.8.x (and in Zope 3)

exactly the same way it was used in 2.7.x.  If it's not working, there
may be a new bug in 2.8.x, but there's been report of that yet.

Because of errors like:

ConflictError: database conflict error (oid 0x0299de, class
Products.DCOracle2.DA.Procedure, serial this txn started with
0x035f0726c7bfca88 2005-08-01 08:38:46.816215, serial currently
committed 0x035f072fed78ebee 2005-08-01 08:47:55.657582)

and according to:
I've added:

def _p_resolveConflict(self, old, saved, new):
   print 'old:', old
   print 'saved:', saved
   print 'new:', new
   return new

to SP.py into procedure class (DA.Procedure extends this),

I've started Zope with runzope and there are no 'old':?, 'new':?,
'saved:?' statements at all on the console although other print
statements from SP.Procedure are visible.

Maybe these conflict errors I'm dealing with are different kind and
are not falling into the correct piece of code or maybe this kind
of test (print 'something') is too stupid to see if _p_resolveConflict
is executed?

Maciej Wisniowski
Zope maillist  -  Zope@zope.org
**   No cross posts or HTML encoding!  **
(Related lists - http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope-dev )

Reply via email to