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... On Apr 28, 2:04 pm, Michael Bayer <[EMAIL PROTECTED]> wrote: > On Apr 28, 2008, at 12:02 AM, Michael Bayer wrote: > > > > > On Apr 27, 2008, at 9:58 PM, BruceC wrote: > > >> I don't know whether this helps, but many thanks for looking at the > >> issue :) > > > unfortunately it doesnt say much at all. You're not sharing a Session > > between multiple threads, right ? > > and by "sharing", I mean the Session, as well as any objects that are > attached to it, since that stack trace illustrated specifically an > attribute lazy-loading its contents from the database. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
