Why don't my south migrations work?

South allows you to create migrations when you first start out with a new app and the tables haven't been added to the database yet, as well as creating migrations for legacy apps that already have tables in the database. The key is to know when to do what.

Your first mistake was when you deleted your migrations, as soon as you did that, and then ran syncdb, Django didn't know that you wanted south to manage that app anymore, so it created the tables for you. When you created your initial migrations and then ran migrate, south was trying to create tables that django already created, and thus your error.

At this point you have two options.

1. Delete the tables for the wall app from your database and then run $ py manage.py migrate wall This will run the migration and create your tables.

2. Fake out the initial migration run$ py manage.py migrate wall 0001 --fake This will tell south that you already have the tables on the database so just fake it, which will add a row to the south_migrationhistory table, so that the next time you run a migrate it will know that the first migration has already been run.

Setting up a brand new project and no database

1. create your database
2. add south to installed apps
3. run syncdb, this will add the django and south tables to the database
4. add your apps
5. for each app run python manage.py schemamigration app_name --initial this will create the initial migration files for your app
6. then run south migrate python manage.py migrate app_name this will add the tables to the database.

Setting up a legacy project and database

1. add south to installed apps
2. run syncdb, this will add the south tables to the database
3. for each of your apps run python manage.py schemamigration app_name --initial This will create your initial migrations
4. for each of your apps run python manage.py migrate app_name 0001 --fake , this will fake out south, it won't do anything to the database for those models, it will just add records to the south_migrationhistory table so that the next time you want to create a migration, you are all set.

Setting up a legacy project and no database

1. create database
2. add south to installed apps
3. for each of your apps run python manage.py schemamigration app_name --initial This will create your initial migrations
4. run syncdb, this will add any apps that don't have migrations to the database.
5. then run south migrate python manage.py migrate this will run all migrations for your apps.

Now that you are setup with south, you can start using south to manage model changes to those apps. The most common command to run is python manage.py schemamigration app_name migration_name --auto that will look at the last migration you ran and it will find the changes and build out a migration file for you. Then you just need to run python manage.py migrate and it alter your database for you.

Hope that helps.

This is how I get things working.

pip install South# add 'south', to INSTALL_APPS, thenpython manage.py syncdb# For existing project + databasepython manage.py convert_to_south app_name# Thereafter, call them per model changespython manage.py schemamigration app_name --autopython manage.py migrate app_name

References:

http://garmoncheg.blogspot.com/2011/08/django-how-and-why-to-use-migrations.htmlhttp://www.djangopro.com/2011/01/django-database-migration-tool-south-explained/

The tutorial you're using states:

(If this fails complaining that south_migrationhistory does not exist, you forgot to run syncdb after you installed South.)

Assuming that your post accurately details the steps you've taken, following that link seems to show that you missed a step before setting up your new app. As you are following a tutorial for setting up migrations on a new application, the order is:

1. Add south to INSTALLED_APPS.
2. Run syncdb.
3. Then follow the tutorial.

I.e., you should've already run syncdb before you added in the models for your new app. Your solution of removing your app from INSTALLED_APPS should work, but it's worth noting that it's really only a "silly" work-around, as you missed a step earlier on. Had syncdb been run before you created the models for that app, you wouldn't have to use the work-around.