[ZODB-Dev] another reason to stop supporting versions

[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?

I will write the necessary tests to fix the undo bug.

Jim

--
Jim Fulton			mailto:jim at zope.com		Python Powered!
CTO 				(540) 361-1714			http://www.python.org
Zope Corporation	http://www.zope.com		http://www.zope.org