On Mar 13, 11:59 am, "Gaetan de Menten" <[EMAIL PROTECTED]> wrote: > I only discovered (or at least understood) this thread localness of > DynamicMetaData, and honestly, I don't understand in what case it can > be useful. It seems like the thread localness is limited to the engine > connected to the metadata. So what I'd like to understand is when > anyone wouldn't want to use a global engine? As long as the > connections are thread-local, we are fine, right?
Not me -- I have cases where the same schema is used with two different databases by two different apps (eg, admin uses a main postgres db and public uses a local sqlite cache), so the current API does what I need, but (if I understand what you're saying) only allowing the connect string of a global engine to vary per request, rather than allowing completely different engines, would not. JP --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
