Django 1.7 migrations won't recreate a dropped table, why?

Go to your database and find the table django_migrations. Delete all the rows which have app equals your app name.

Then do a makemigrations & migrate will work.

Another solution I've found and works perfectly:

In django 1.7:

1. Delete your migrations folder

2. In the database: DELETE FROM django_migrations WHERE app = 'app_name'.

   You could alternatively just truncate this table.

3. python manage.py makemigrations

4. python manage.py migrate --fake

In django 1.9.5:

1. Delete your migrations folder

2. In the database: DELETE FROM django_migrations WHERE app = 'app_name'.

   You could alternatively just truncate this table.

3. python manage.py makemigrations app_name

4. python manage.py migrate

This works 100% for me!

Migrations check for differences in your models, then translates that to actions, which are translated to SQL. It does not automatically sync the db scheme with your models, and it has no way of knowing you dropped a table (it doesn't know about manual changes because, well, you're not supposed to do manual changes. That's the point)

The answer? a manual change requires a manual migration as well. What you need to do is simply write your own migration and manually tell south to re-build the table. It's not very difficult, The docs make it pretty easy. Just make something like this:

from django.db import migrations, modelsclass Migration(migrations.Migration):    operations = [        migrations.CreateModel("Foo"),        migrations.AddField("Foo", "bar", models.IntegerField(default=0))    ] 

You can probably look into the first migration file (the one that made the model in the first place) and copy paste almost all of it. Then all you have to do is run the migration like you always do