Well, you know...
In this one project, we had an interesting (cough) situation with
PostgreSQL + psycopg, where we would see plenty of write conflict
errors coming from the DB connector.
Turned out PostgreSQL has kind of an "optimistic" transaction
control, where the DB server returns something like "couldn't really
resolve this concurrency issue, please retry" to the DB connector,
and psycopg would translate that into a ZODB ConflictError to make
the ZPublisher retry the transaction. Not kidding.
So, while I don't know much about the internals of DCOracle you may
want to make sure the ConflictErrors are due to the ZODB at all.
Stefan
On 7. Aug 2005, at 23:50, Tim Peters wrote:
If you want to dig deeper, look into what happens inside
lib/python/ZODB/ConflictResolution.py
I'll try to check this, thanks for the hint. :)
It's the only way you'll figure it out ;-)
--
Anything that happens, happens. --Douglas Adams
_______________________________________________
Zope maillist - Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope-dev )
