On Tuesday, April 3, 2018 at 11:41:43 AM UTC-4, Mike Bayer wrote: > > right, the dispose() will emit "close connection" commands on the > socket which will leak into the parent process. >
But only if `close()` has been called -- right? > they're not ! :) that's one of the "features" of QueuePool. only > when they get checked in again does the QP have any idea who they are. > > I wrote an alternative pool some months ago that works identically to > QueuePool but does the more traditional approach of having a fixed > "slot" for every possible connection. That would be a nice pool to > use someday, but unfortunately doesn't have the ten years of > production use by thousands of applications behind it. > Makes perfect sense. I'm surprised I couldn't find a debugging version of the Queue Pool that just notes the object ids as text (this way there's no reference). Like most things SqlAlchemy, It's probably in there but I missed it. -- SQLAlchemy - The Python SQL Toolkit and Object Relational Mapper http://www.sqlalchemy.org/ To post example code, please provide an MCVE: Minimal, Complete, and Verifiable Example. See http://stackoverflow.com/help/mcve for a full description. --- 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 https://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
