[Zope3-dev] substransactions and beforeDelete

Jim Fulton jim at zope.com
Wed Jan 7 15:05:48 EST 2004

Steve Alexander wrote:
>> Thats fine. Just call get_transaction().abort(). You just want to
>> make sure that there isn't any other code doing work you don't know
>> about.
> Isn't it the case in ZODB 3 that a new transaction is implicitly started 
> after an abort?


> I remember a thread on zodb-dev many months ago about wanting to doom a 
> transaction so that it will definitely be aborted later, without 
> actually aborting it now.

Sounds cool. :)

You could do this as a hack now, by faking a read conflict. I assume
that this could be generalized.


Jim Fulton           mailto:jim at zope.com       Python Powered!
CTO                  (540) 361-1714            http://www.python.org
Zope Corporation     http://www.zope.com       http://www.zope.org

More information about the Zope3-dev mailing list