No, we just exclude objects with _v_ attribute from mid-transaction deactivation. There arent many objects in that category, but they do need protection.
This is slightly OT but reminded me of something important I need to ask.
ZOracleDA stores its database connections in a _v_ variable on the DA object. It tries to delete this by setting the _v_ variable to None.
However, a number of people have noticed that the Oracle connections aren't going away from the Oracle server's point of view.
In most cases, however, they do go away when the ZODB cache is cleared.
What in the ZODB cache or other ZODB code could be causing _v_ variables to stick around after they've been set to None in their containing objects?
Zope-Dev maillist - [EMAIL PROTECTED]
** No cross posts or HTML encoding! **
(Related lists - http://mail.zope.org/mailman/listinfo/zope-announce