On May 22, 2011, at 5:43 AM, Faheem Mitha wrote: > [This message has also been posted.] > On Fri, 20 May 2011 09:44:36 -0400, Michael Bayer <[email protected]> > wrote: > >> OK so not just schema names, table structure as well. So yeah so >> you're using the same classes among entirely different databases >> essentially, so yeah just like our tests do, just tear down before >> remapping for a new DB and you're done. > > Hi Michael, > > Ok, thanks for the suggestion. Can you point me to a place in your > unit tests where this tear down happens?
this is in test/lib/fixtures.py > > Also, can you reply regarding the 'tometadata' thing? Not super > important, but I'm just curious about what it does, exactly. Thanks. I don't really understand the questions you've asked there. table.tometadata() makes a copy of "table", where "table" is a sqlalchemy.schema.Table object, linked to a new MetaData, and returns to you the newly generated sqlalchemy.schema.Table object. If you need a list of Table objects to go through this procedure then yes a loop is how you'd do that.... -- 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.
