The conflict almost always happens in the storage (FileStorage, for instance) or at other places in the ZODB code itself. A conflict happens at transaction boundaries unless it's a read conflict which can happen at any time. So having the line number is not really all that helpful. That said, you *can* get it by setting STUPID_LOG_SEVERITY to -100. On Mon, 28 Jan 2002 13:20:22 +0100 Thomas Guettler <zopestoller@thomas-guettler.de> wrote:
I recieve conflict writes:
"conflict error at foo (X conflicts since startup)"
Is it possible to get the line of the number where the conflict happend?
Background:
I have a python product with a class that uses a BTreeFolder to store many documents. All files in my simple DMS store the data in this directory.
thomas
_______________________________________________ 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 )