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.
Oh thanks, I hadn't dug that deeply into FSQLA yet. This is narrowing down the issue though. Our anecdotal experience is that pool_recycle is not doing anything with Oracle... hopefully have a test (or ideally a "never mind") follow up in a few days. Am I correct in assuming that SQLA connection pool is wholly independent of Oracle's connection pooling (which we have disabled)? Ben > > -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To view this discussion on the web visit https://groups.google.com/d/msg/sqlalchemy/-/jPrqeF15RZcJ. 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.
