Hi ! Was just talking to Vlad over on the SQLAlchemy list. What is needed in this case is the ability to use SQLAlchemy's "begin_nested()" method, which emits a "SAVEPOINT" instruction against the relational database. When using this feature, the next call to rollback(), assuming the "nested" status is still in progress, will "ROLLBACK TO SAVEPOINT". My understanding is that we just need to know how to use this feature when using the zope.transaction extension to manage transactions. In particular, if zope.transaction intercepts calls to "Session.rollback" and prevents them, it needs to either provide its own means of managing a "nested" SQLAlchemy transaction, or needs to recognize SQLAlchemy rollback() calls that are in fact against a "nested" transaction, which would be via some further introspection on the SQLAlchemy session when the event is intercepted.
At some point I'll have the opportunity to work with zope.transaction firsthand and then we'll no longer need to educate zzzeek about such things. Until then please bear with me ! -- You received this message because you are subscribed to the Google Groups "pylons-discuss" group. To view this discussion on the web visit https://groups.google.com/d/msg/pylons-discuss/-/Jmji6_ohyCYJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/pylons-discuss?hl=en.
