[ZODB-Dev] [ zodb-Bugs-631680 ] Error in objects un-created due to undo
SourceForge.net
noreply@sourceforge.net
Fri, 17 Jan 2003 11:42:44 -0800
Bugs item #631680, was opened at 2002-10-31 17:56
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=115628&aid=631680&group_id=15628
Category: None
Group: None
>Status: Closed
>Resolution: Fixed
Priority: 5
Submitted By: Magnus Lyckå (mly)
Assigned to: Jeremy Hylton (jhylton)
Summary: Error in objects un-created due to undo
Initial Comment:
If an object is created in a transaction, and this
transaction is removed with db.undo(), the object is so
to say "un-created" (or George Bailey'd) in the database.
It might still exist in the running program though. If
you try to access attributes of this object using
FileStorage, you will get "error: unpack str size does
not match format" with Python 2.2, and "OverflowError:
long int too large to convert" with Python 2.1. Correct
error (as seen in Berkeley Full storage) would be a
KeyError.
(I'm not sure whether anything else regarding these
objects should be handled differently.)
Test script that will trigger the error is attached.
----------------------------------------------------------------------
>Comment By: Jeremy Hylton (jhylton)
Date: 2003-01-17 19:42
Message:
Logged In: YES
user_id=31392
This was fixed.
----------------------------------------------------------------------
Comment By: Jeremy Hylton (jhylton)
Date: 2002-11-20 18:41
Message:
Logged In: YES
user_id=31392
I believe this will be fixed in 3.1.1. Would you be able to
check against the CVS version of ZODB in ZODB3_3-
1_branch?
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=115628&aid=631680&group_id=15628