mozilla/kitsune — pull request #1609 by willkg (2013-09-10 02:14:26+00:00)
Title: Reset schema 911831

To test, I did something like this:

1. run ``vendor/src/schematic/schematic migrations/`` to do the last schematic migration
2. run ``./manage.py migrate`` which should be a no-op
3. change the database name in your `settings_local.py` file to a new one, create the new database and then do ``./manage.py syncdb --migrate`` which is what the hacking howto says to do to create a fresh db now
4. get a new db dump and run the above two things on it

Clearly step 4 takes forever. You can probably skip it since steps 1 and 2 cover it for the most part.

The one thing that's not tested is the deployment script changes. Definitely worth checking the command lines, but otherwise we'll have to wait until this gets to -dev to test.

The one thing this doesn't touch is the admin page that shows the schema version. I need to think about that. We could continue to show the schema version until we dump schematic and additionally show the south_migrationhistory table. Thoughts on that are welcome.

When this lands, I'll write an email that talks about the changes at a high level and highly encourages everyone to spend some quality time with the South tutorial.

One sucky thing about switching to South is that it creates migration code that's not PEP-8 kosher. So if you have a pre-commit hook that prevents you from committing things that aren't PEP-8 kosher, you might want to ditch it.

r?