Am Dienstag, den 24.04.2007, 17:01 -0400 schrieb Jim Fulton:
> I'm 99.9% sure that version commit and abort are broken in ZODB.DB.   
> The commit methods in CommitVersion, and AbortVersion (and  
> TransactionalUndo) call invalidate on the databse too soon -- before  
> the transaction has committed.  This can have a number of bad  
> effects, including causing inconsistent data in connections.
> An argument for keeping version in the past was that they "worked".   
> Well, I think they don't work and I'm not interested in writing the  
> test to fix them.  Is anyone else?

Nope. However. We deprecated versions in Zope 2 a while ago disabling
the ability to add new versions but keeping existing versions alive.

We have to tell people what to do before the next update of Zope that
includes this change so they do not get locked out of existing data.

Unfortunately we have no numbers on how many people use versions. I
think I'll raise that question on Zope users and the German users list
to get a feeling on how many people react.


gocept gmbh & co. kg - forsterstra├če 29 - 06112 halle/saale - germany
www.gocept.com - [EMAIL PROTECTED] - phone +49 345 122 9889 7 -
fax +49 345 122 9889 1 - zope and plone consulting and development

Attachment: signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil

For more information about ZODB, see the ZODB Wiki:

ZODB-Dev mailing list  -  ZODB-Dev@zope.org

Reply via email to