Hi List, I had a bit of trouble figuring out how sqlalchemy-migrate worked at first, but now that I've got it, it seems pretty useful. But because we require default data for one of our pylons apps, but not the another, our installation processes were different. In the former, we would do this:
paster setup-app manage.py version_control <VERSION> In the latter: manage.py version_control manage.py upgrade This caused a bit of confusion when people who were unfamiliar with sqlalchemy-migrate used both our apps. So to streamline it, we are trying out integrating SA-migrate into our setup_app method. Now at the end of setup_app, we use the SA-migrate API to lookup the max version, and create version_control on the db using that version. Is anyone else doing something similar? Any tips or pitfalls I should know about? -- 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.
