On Feb 17, 2014, at 9:27 PM, Claudio Freire <[email protected]> wrote:
> > This is exactly what I need, thanks. Furthermore, with psycopg2 level > autocommit, I don't think I even need a second statement-based pool, > it will decrease idle-in-transaction time on its own. In fact, I > thought this is what execution_options(autocommit=True) did, though > looking at the code, now I realize it wasn’t. right, we currently don’t link the SQLAlchemy-level “autocommit” things with a DBAPI-level autocommit. Not all DBAPIs have an autocommit option as it isn’t in the spec and I’m generally just concerned about how wide of a behavioral difference there’d be between different backends if we sometimes used their autocommit, sometimes, ours, etc.
signature.asc
Description: Message signed with OpenPGP using GPGMail
