This is a normal error. It means that two threads are updating the same object at the same time. See the Zope Developer's Guide "Persistence" chapter for more information. ----- Original Message ----- From: "Sven Rudolph" <rudolph@medical-tribune.de> To: <zope@zope.org> Sent: Thursday, September 19, 2002 10:12 AM Subject: Re: [Zope] ZODB Conflict Error ?
Hello Gitte,
Zope Version: (unreleased version, python 2.1.3, linux2) (We are running it from cvs - branch name is: Zope-2_5-branch)
Python version: 2.1.3 (#2, Apr 15 2002, 12:14:12) [GCC 2.96 20000731 (Linux-Mandrake 8.0 2.96-0.48mdk)]
Python-2.1.3 is OK but I am not sure if Zope-2_5-branch includes 2.5.1.
Before we updated to Python-2.1.3/Zope-2.5.1 we had some very weird bugs and even data loss. But they all vanished after upgrading. So I suggest you make sure you are running Zope-2.5.1
Another thing you should try is packing the database with days=0.
Greetings
Sven
-- Sven Rudolph, Programmierer GermanMedicalServices.de GmbH Unter den Eichen 5, 65195 Wiesbaden Tel.: 06 11 / 97 46 25 2
_______________________________________________ Zope maillist - Zope@zope.org http://lists.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope-dev )