a given application makes explicit use of `commit` and `rollback` on the sqlalchemy session.
a few views require interaction with some other technologies via a two-phase commit. under the current design, i can't enable two-phase commits for everything. i'm not sure I can detect the need for a two-phase commit early enough to use a dedicated session object. on postgresql (at least), the two-phase commit arguments don't appear to be needed until it's ready to commit. I have a hope this might be possible, but alternatives if not (postgres is the only "member" that could veto transactions in this application) -- SQLAlchemy - The Python SQL Toolkit and Object Relational Mapper http://www.sqlalchemy.org/ To post example code, please provide an MCVE: Minimal, Complete, and Verifiable Example. See http://stackoverflow.com/help/mcve for a full description. --- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at https://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
