checkCreativeGetState tests the wrong fix to a problem
Bug #485456 reported by
Jim Fulton
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ZODB |
Fix Released
|
Medium
|
Unassigned |
Bug Description
When an object modifies itself in __getstate__, it's state get's written twice. This is a bug in ZODB (Connection or serialize).
Storages should not have to tolerate this. Typically what happens is that multiple states get written for the object. The decision of which one to use is arbitrary. Presumably, checkCreativeGe
This is somewhat related to https:/
Changed in zodb: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
To post a comment you must log in.
This may have been fixed by the fix to https:/ /bugs.launchpad .net/zodb/ +bug/185066. We need to write (or find :) a test to verify this.