On Apr 10, 2007, at 7:44 AM, Manlio Perillo wrote:
> > Yes. > From the documentation it is not clear if this is allowed. > the word "threadlocal" means that a resource is tied to the current thread. therefore, if you take resources which expect this behavior and then send them off to three different threads during their lifecycle, they will not have consistent access to the resources they require. "threadlocal" strategies are not compatible with sharing those objects between threads - they are designed to allow "global" resources that are automatically held within the scope of a thread. with twisted, nothing except your initial engine (and metadata, Tables) should be held in a global scope, everything else (sessions, connections, transactions) should be declared and torn down within a local scope. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
