On Feb 9, 2012, at 3:02 PM, Chris Withers wrote: > Almost, but... > > We can't have per-connection models, that would be semantically weird. > Using a different metadata at session creation time, keyed off the dsn of the > database connected to, and with irrelevant classes blowing up if used but > ignored otherwise is semantically what I'm after. Clues as to how to > implement gratefully received...
do you have multiple, simultaneous engines when the app runs, where some engines might not be available, or just one engine, pointing to a database that has some subset of required tables ? this is confusing me. what's not working with the try/except on the reflection ? -- 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 sqlalchemy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
