How to simplify migrations in Django 1.7?

django django-migrations django-1.7
Kit Fisto picture Kit Fisto · May 20, 2014 · Viewed 93.1k times · Source

There are already similar questions for South, but I have started my project with Django 1.7 and am not using South.

During development a lot of migrations have been created, however the software is not yet delievered and there exists no database that must be migrated. Therefore I would like to reset the migrations as if my current model was the original one and recreate all databases.

What is the recommended way to do that?

EDIT: As of Django 1.8 there is a new command named squashmigrations which more or less solves the problem described here.

Answer

kzorro picture kzorro · Nov 19, 2014

I got this. I just figured this out and it is good.

  • First, to clear migrations table:

    ./manage.py migrate --fake <app-name> zero

  • Remove app-name/migrations/ folder or contents.

  • Make the migrations:

    ./manage.py makemigrations <app-name>

  • Finally tidy up your migrations without making other database changes:

    ./manage.py migrate --fake <app-name>

Related questions

Django 1.7 - makemigrations not detecting changes

As the title says, I can't seem to get migrations working. The app was originally under 1.6, so I understand that migrations won't be there initially, and indeed if I run python manage.py migrate I get: Operations to perform: Synchronize …

Read More
django 1.7 migrate gets error "table already exists"

I am trying to apply a migration but am getting the error: django.db.utils.OperationalError: (1050, "Table 'customers_customer' already exists") I get this by issuing the following command: python manage.py migrate My customer table already exists, so what …

Read More
How to add a new field to a model with new Django migrations?

I'm using the contribute_to_class method but I don't know how to create the field in the database with new migrations.

Read More