[sqlalchemy] Debugging recycled pool connections

First let me make sure that I understand what the recycle parameter does in the pool. Lets say I have a session i never close(), or even a query that exceeds this recycle limit to return . When this recycle parameter limit is reached the connection will automatically be closed removed from the

Re: [sqlalchemy] Debugging recycled pool connections

On Jan 2, 2014, at 9:38 AM, John Kida jdk...@gmail.com wrote: First let me make sure that I understand what the recycle parameter does in the pool. Lets say I have a session i never close(), or even a query that exceeds this recycle limit to return . When this recycle parameter limit is

[sqlalchemy] Re: Debugging recycled pool connections

Thanks for replying so fast. I understand using the event system to track the stack trace, however how would you recommend implementing a timeout for checked out connections, to find connections stuck in a checked out state? I dont think I would actually use this in production, but on a

Re: [sqlalchemy] Re: Debugging recycled pool connections

On Jan 2, 2014, at 10:40 AM, John Kida jdk...@gmail.com wrote: Thanks for replying so fast. I understand using the event system to track the stack trace, however how would you recommend implementing a timeout for checked out connections, to find connections stuck in a checked out state?

[sqlalchemy] sqlacodegen 1.1.4 released.

This release fixes compatibility with the just released SQLAlchemy 0.9.0 final. -- 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