savepoint state survives across close

Bug #143561 reported by Tim Peters
2
Affects Status Importance Assigned to Milestone
ZODB
Fix Released
Low
Unassigned

Bug Description

See thread here:

<http://mail.zope.org/pipermail/zodb-dev/2005-November/009427.html>

The attached `what.py` is a simplified test case. In general, the current transaction should be committed or aborted before closing a connection. This code doesn't. But ZODB doesn't raise ConnectionStateError in this case, nor does it manage to clean up all the bits left behind by the savepoint that got made. This causes "crazy" errors later.

Tags: bug database
Revision history for this message
Tim Peters (tim-one) wrote :
affects: zope2 → zodb
Changed in zodb:
importance: Medium → Low
Revision history for this message
Jim Fulton (jim-zope) wrote :

This was fixed a while ago.

Tested just now w trunk and 3.9.

Changed in zodb:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Bug attachments

Remote bug watches

Bug watches keep track of this bug in other bug trackers.