here's what i do: - I always and only use table reflection - I have a table called 'appschema' that is roughly in pg:
create table app_schema ( id serial, component varchar(32), schema_version int, timestamp_install timestamp ); create unique index app_schema_uidx on app_schema( lower(component), schema_version ); - in my app i have a toplevel dir called 'sql-migrations' that just has this structure component/id-desc.sql - the last line of every migration file inserts a new app_schema line. the files are just raw sql commands that can be piped to the db directly. - in my code, i note what components schema versions are needed on bootup, and i make sure its in the db it's a bit of work -- and i'd like to automate it at some time -- but it makes dealing with schema changes across deployments and dev environments relatively simple. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pylons-discuss" 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/pylons-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
