That is what I am trying to figure out. It works perfectly when I do this. On 7/20/07, Michael Bayer <[EMAIL PROTECTED]> wrote: > > > > On Jul 19, 2007, at 5:06 PM, Arun Kumar PG wrote: > > > or may be just keep on using the QueuePool approach as it will > > always make sure to return the same connection to the current thread ? > > > > like i said, i dont see how that helps any. a single Session thats > in flush() holds onto a single connection and returns it regardless > of what thread accesses it. the threadlocal pool setting doesnt have > any effect on threadsafety. > > > > > >
-- Cheers, - A --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
