On Oct 16, 2012, at 5:56 PM, Ben Hitz wrote: > Has anyone ever tested the pool_recycle in Oracle when a user has a maximum > idle time? We are having an issue with a flask/sqla/cx_oracle stack where > when the DB_USERs idle time expires, Oracle throws us: > > ORA-02396: exceeded maximum idle time, please connect again. Which is no big > deal... except in flask the connection is done at start up
that's not entirely accurate. The Flask-SQLAlchemy extension checks out a connection from the connection pool at request start, returns it at request end. The pool is responsible for dealing with the lifecycle of database connections and can be confiugured to deal with this. To deal with connections that time out after a certain time idle, use the pool_recycle option: http://docs.sqlalchemy.org/en/rel_0_7/core/pooling.html?highlight=pool_timeout#setting-pool-recycle . -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com. To unsubscribe from this group, send email to sqlalchemy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
