Setting _p_changed of a Blob with no uncomitted changes causes error
Bug #440234 reported by
Patrick Strawderman
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ZODB |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
The following reproduces this issue:
blob = ZODB.blob.
conn.add(blob)
transaction.
blob._p_changed = True
transaction.
Connection is passing the result of blob._uncommitted() to ClientStorage.
but gets None instead. A TypeError is eventually raised in ZODB.blob.
I'm not sure what the correct behavior is here, but this case should probably handled.
Changed in zodb: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
I'm inclined to consider the correct behavior undefined.
Why do you think someone would set _p_changed on a blob?