[egenix-users] Zope mxODBC DA - ConflictError Problem

Philip Kilner phil at xfr.co.uk
Mon Jul 17 11:09:34 CEST 2006


Hi Marc-Andre,

M.-A. Lemburg wrote:
> Which Zope version are you running ?
> 

Zope version is currently 2.8.6.

> Do you use connect-on-demand for the connection in question ?
> 

No, this connection is open all the time.

FWIW, since asking for help here, it has been suggested that these
conflict errors may be related to long transactions, and I have had some
success at reducing their frequency by addressing query performance on
the db side.

> The Zope DA can generate lots of debug output if needed:
> 
> To enable debugging output in the mxODBC Zope DA, you have two
> options:
> 
> 1. set the _debug global variable from within Zope, e.g. via
>    an external method:
> 
> def enable_mxODBCZopeDA_debugging(container):
>     from Products.mxODBCZopeDA import ZopeDA
>     ZopeDA._debug = 3
> 
>    and call that method once after Zope startup. Note that
>    the setting will not persist across Zope startups.
> 
> 2. create a file ZopeDASettings.py in the directory
>    Products/mxODBCZopeDA (the same directory where you
>    find the ZopeDA.pyc file):
> 
> ### Adjust ZopeDA global settings:
> #
> # Enable verbose debugging output:
> _debug = 3
> #
> # Optionally enable leak testing (this let's the driver
> # always return an empty result set and can be used to
> # track connection related leaks)
> _leak_testing = 0
> 
>    The mxODBC Zope DA will pick up this file upon
>    restart of Zope and set the globals accordingly.
> 

Thanks - I'll have a go at this, initially outside working hours...


-- 

Regards,

PhilK

"Human language continually changes, innit."
- Stephen Juan



More information about the egenix-users mailing list