Is create_engine supposed to return the same engine if it's given the same connection string (using either plain or threadlocal strategy)
rev 2102 returns a new engine each time, hence I get a new pool every time, and my app consumes all available firebird connections because those connections don't get closed. echo_pool shows new connections created, checked out of pool and put back into a pool. I don't retain a handle to the engine, yet when it goes out of scope it doesn't seem to retire the pool, or maybe when the pool gets gc'd, it's not releasing the connections it still holds. -- I thought at one time create_engine would return the same engine instance each time it's called with the same connection string. That seems to not be the case anymore (if it ever was) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en -~----------~----~----~----~------~----~------~--~---
