Thanks, I'll take a look. On Wed, 23 Nov 2005, Michael Dunstan wrote:
> On 11/22/05, Florent Guillaume <[EMAIL PROTECTED]> wrote: > > Dennis Allison wrote: > > > *** you are correct -- this is the easy hack on the event.log. It's much > > > harder to know how many make it out to the user. We have an associated > > > bug in the MySQL interface which generates threading errors, apparently > > > triggered by a conflict error and the subsequent backout. These occur > > > with most conflicts which involve the database--almost every conflict with > > > our system structure. > > > > I'm actually not sure what's logged when a Conflict Error makes it back > > to the users, offhand I don't see anything in my logs. Can someone > > confirm or infirm that fact? > > > > If nothing is logged, I'll add something at level ERROR. > > > > BTW does someone have a handy script to provoke conflict errors on a > > naked Zope? > > There is a doctest that might be useful here. See the last half of > testPublisher() in lib/python/ZPublisher/tests/testPublish.py which > tests the behavior of the publisher in the face of one or more > ConflictErrors. > -- _______________________________________________ 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 )