On Apr 28, 2008, at 4:04 AM, BruceC wrote:
> > We're not intentionally sharing a session between multiple > threads... :) I'll check out the code to see if there is any sharing > going on, but I'm pretty sure that's not the case. > > You mention lazy-loading as if it might be playing a part in this > issue - is that right? We are using lazy & eager loading in various > parts of the app... the lazy loading can present an issue only to the degree that the object still maintains a link to its originating Session. So if the lazy loader fires off in a thread other than that where the Session normally resides, you can have concurrent access to it, which in the case of the Session already being within a transaction, could create concurrent access on a single connection. Basically if you dont share anything between threads, in theory this kind of issue should not occur. --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
