Thx all NullPool solve my problem create_engine(cnx_str, poolclass=NullPool)
2014-02-07 19:11 GMT+01:00 Claudio Freire <klaussfre...@gmail.com>: > On Fri, Feb 7, 2014 at 2:35 PM, Michael Bayer <mike...@zzzcomputing.com> > wrote: > >>> 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). > > > > that kind of thing generally happens to people when they aren't cleaning > up their sessions, or are using awkward engine/connection patterns. the > pool has had a lot of bugs fixed but I haven't seen a bug where the pool > isn't emitting the rollback when the connection is marked closed. > > There was an awkward pattern involved: using the session's connection > as returned by Session.connection() manually to issue some textual > SQL. Other than that, normal thread-local session stuff. > > -- > 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. > -- 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.
