[egenix-users] Help! - mxODBCZopeDA 1.0.9 breaks my Zope 2.8.1

Charlie Clark charlie at egenix.com
Tue Aug 16 13:21:01 CEST 2005

On 2005-08-16 at 06:09:23 [+0200], Daniel W. Adair <danny at asterisk.co.nz> 
> Has anyone have similar experiences?
> Where can I look for a solution?
> It seems to me like something that needs to be persistently stored in
> the ZODB isn't...
> Was mxODBCZopeDA thoroughly tested with Zope 2.8.1 and the new ZODB version?
> This is for a client, and they need to use the database connection every
> day (including today :-().
> Please help.


thanks for pointing this out to us. The problem is indeed related to the ZODB 
change which we hadn't picked up on our tests. We will send you a patched 
.pyc of the DA.

Regarding the general release strategy it looks like we are going to have to 
drop our support for all possible versions of Zope due to the pace of 
releases of Zope - a new release every six months according to release 
manager Andreas Jung - and the significant changes in architecture. We're 
proposing to release a fixed version of the DA for Zope 2.6, 2.7 and 2.8 with 
other versions available only on request and want to know what your reaction 
is. Do we have heavy uses of mxODBCZopeDA on older versions of Zope who are 
not able to migrate to one of these versions?

Regarding mxODBCZopeDA we are currently evaluating this. Because Zope X3 has 
a different architecture we would currently have to do a separate product 
release solely for Zope X3. We have to wait for architecture to settle before 
beginning on this. Hopefully we will be able to write an mxODBCZopeDA for 
Zope 3 which will then run on Zope 2.x + FIVE. In the meantime the new 
architecture does make it fairly easy for developers to write their own DA 
based on mxODBC. It would be useful for us in our planning to hear your 
proposed migration strategies.


More information about the egenix-users mailing list