Hi Mike, >ive thought about this, and the Query is not in fact tied very hard to >a partcular Session (or at all). I think it would be workable for us >to add a "using_session()" method to it, i.e.: > > The original workaround you suggested of using a callable works fine for now. A using_session method would be nice, avoid exposing this detail to the user of my widget. Although pretty soon after I made the change I found a separate advantage of using a callable, so I'll probably stay with that. I guess another option is to make the query bind to the scoped_session object, so it picks up an appropriate session when it actually uses it.
Thanks for taking a look, Paul --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
