Michael Bayer wrote: > the SQLAlchemy engine corresponds to a single connection URL. if you > want to close all connections, call dispose() on the engine. >
OK, calling dispose() on the engine seems to work just fine. I've noticed that there are always two connections though, even in this simple scenario. Is that normal? During my processing I obviosuly select stuff, modify it and save it back using a session. If I turn on INFO level logging I can see that SA is also putting one of these connections into the pool and immediately getting it out again between the SELECTs and the UPDATEs or INSERTs. This kind of implicit pool swapping seems a bit inefficient. Works just fine though so I can't really complain :) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
