Michael Bayer wrote: > > On Oct 24, 2006, at 10:46 AM, Gary D wrote: >> 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? >> > > the pool does not create any connections until called. if two > connections are getting created, it would imply two operations are > going on , where the second operation starts before the first has > closed its Connection proxy. >
Hmm, this is a single threaded utility program that just goes start to finish in a select, modify / (update or insert) cycle of several tables. I can't see how two operations would overlap. Is it possible that SA has taken out a connection to do the update/inserts while keeping the original one that started off with a select? It's also possible I guess that I missed closing a resource (cursor?) somewhere. I'll investigate further. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
