Yes, the South documentation describes how to do it, but basically just add this to your settings.py file: SOUTH_TESTS_MIGRATE = False # To disable migrations and use syncdb instead SKIP_SOUTH_TESTS = True # To disable South’s own unit tests
So the step-by-step plan I outlined in my question does work, but instead of deleting rows from the south_migrationhistory database table, I had to delete rows from the django_migrations database table. The command is: DELETE FROM django_migrations WHERE app=’my_app’ Once this is done, you will be able to re-run your migrations from scratch.
You need to make manage.py executable to excecute it. Do chmod +x manage.py to make it excecutable. Alternately you can do python manage.py <cmd> instead.
Agreed, your model is probably wrong. The formal primary key should always be a surrogate key. Never anything else. [Strong words. Been database designer since the 1980’s. Important lessoned learned is this: everything is changeable, even when the users swear on their mothers’ graves that the value cannot be changed is is truly a natural … Read more
./manage.py migrate myapp zero See: https://docs.djangoproject.com/en/1.9/ref/django-admin/#migrate In Django 1.11: https://docs.djangoproject.com/en/1.11/ref/django-admin/#migrate
According the Polls tutorial: python manage.py makemigrations <app>: Create the migrations (generate the SQL commands). python manage.py migrate: Run the migrations (execute the SQL commands).
Updated answer for Django migrations without south plugin: Like T.T suggested in his answer, my previous answer was for south migration plugin, when Django hasn’t any schema migration features. Now (works in Django 1.9+): T.T wrote: You can try this! python manage.py makemigrations python manage.py migrate –run-syncdb Outdated for south migrations plugin As I can … Read more
South does not track django.contrib.auth permissions. See ticket #211 for more information. One of the comments on the ticket suggests that using the –all option on syncdb may solve the problem.
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 … Read more
Changing the field name while keeping the DB field Adding an answer for Django 1.8+ (with Django-native migrations, rather than South). Make a migration that first adds a db_column property, and then renames the field. Django understands that the first is a no-op (because it changes the db_column to stay the same), and that the … Read more