I knew I should've been more explicit On Fri, Feb 7, 2014 at 1:07 PM, Michael Bayer <mike...@zzzcomputing.com> wrote: > On Feb 7, 2014, at 11:01 AM, Claudio Freire <klaussfre...@gmail.com> wrote: > > > I've had similar issues with 0.7.10. SA opens an implicit transaction, > > > incorrect, DBAPI does this, please see: > http://www.python.org/dev/peps/pep-0249/#commit
Ok, yeah. The point is, it's open. > and neither Session.remove nor Session.close really roll back the > transaction No, but the connection pool should. (reset_on_return, which I have enabled) > The connection pool, if in use, will then not > actually "close" the connection if it is to remained pooled, it calls > rollback() as part of the pool release mechanism. Recent versions of > SQLAlchemy allow this to show up in the engine logs like any other rollback, > so you probably wouldn't have noticed. And *this* is what was not happening. Somehow, transactions remained open on the database (I checked). -- 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 http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/groups/opt_out.
