I haven't used South as much as I should have (instead I have painful > manual scripts to do migrations). The biggest pain point about > database schemas for me is easily test database setup. That is, sync > from scratch. I do the following currently: > 1. load schema + a little bit of data from production through > pg_dump + pg_restore. The data is mostly metadata, in particular > already applied migrations in production. > 2. run those migrations that haven't been applied already. > > Will I be able to do the above somehow? Will #3 do a similar thing > for test database setup, except that you run all migrations against > empty database? The first migration would be the initial "syncdb", and > then you run rest of the migrations in chain finally arriving to the > wanted database state. Or would it be "sync" all models, then run > migrations against that database? > > Sorry if these are stupid questions... I really do not know South as > well as I should, so I need a little tutoring...
The way South works, and the way this will work (for new installs as well as tests) is that if migrations are present for an app, it will always create new databases by running through them from the very first migration to the latest one. The proposed "squash" feature helps stop any potential long setup times (from hundreds of migrations) by allowing you to replace 100 old ones with a few new ones, optimised to have less operations. Andrew -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
