[sqlalchemy] Re: physically disconnecting

[Michael Bayer]

On Oct 24, 2006, at 1:45 PM, Gary Doades wrote: 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? im guessing you are using some implicit executions...you should take a look at http://www.sqlalchemy.org/docs/dbengine.myt#dbengine_implicit to understand their behavior. Also if you look in the file test/testbase.py, you will see a connection pool class called MockPool, which you can use yourself and it will raise an exception the instant a second connection is allocated.  Im pretty confident straight query/session usage is good here, since I can run most ORM unit tests using this pool and i get no errors. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalchemy@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sqlalchemy -~----------~----~----~----~------~----~------~--~---