On Mar 6, 2008, at 1:30 PM, Jonathan Vanasco wrote:
> So my result is this: > > - I already have 5 engines. > - I currently have 1 Metadata. I could push this to 5. In my > instance, it doesn't seem to matter. > - I should have 5 Session > > What has really tripped me up , is the way the orm.mapper and sa.Table > work with one another in this. I'm going to have to play with this a > bit more... > Some config is stored in MetaData and others in the Model Class > definitions , so depending on whether i use 1 or 5 metadata items I'll > have to do a convoluted mess to get the multiple metadata's configured > right with sa.Table and orm.mapper ( because of storing the table def > per connection, checking for it, and mapping it). If that sounds > confusing, thats because I'm half lost on this still. But I think i > can figure something out today. with the metadata, just forget about the metadata being associated with a database in any way. if your app deals with a set of tables that all have some relation to each other, just have one metadata, dont bind it to an engine and just forget that its there. the same Table objects should be used across all of your databases- its the specfic engine in use with a particular statement execution that would differentiate what actual database is being accessed. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
