Michael Bayer wrote: > >> What if they exist but don't match the spec that SA has created? > > just try it out...create_all() by default checks the system tables for > the presence of a table first before attempting to create it
Cool, > (same > with dropping). When would SA drop a table? > this is controlled by a flag called "checkfirst". This a parameter to the methods or does it need to be set in some config file? > if you're concerned about people running your application against > databases created from a different version and then failing, I would > suggest adding a "version" table to your database which contains data > corresponding against the version of your application in some way. Good plan. > There has been interest among some SA users over building a generic > "schema comparison" system and I think even some prototypes are > available, though I think thats a fairly complicated and unreliable > approach to take for this particular issue. Do the projects have a name? cheers, Chris -- Simplistix - Content Management, Zope & Python Consulting - http://www.simplistix.co.uk --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---