Logo Questions Linux Laravel Mysql Ubuntu Git Menu
 

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

Using Django 1.7 migrations.

I accidentally dropped a table in my database. I assumed that by running migration again this would recreate the table but no, Django states "No migrations to apply".

How to I get Django to recreate the table?

I have run:

> makemigrations - No changes detected
> migrate - No migrations to apply.

I have tried making a change to the model and running a new migration and it simply states that "Table 'x.test_customer' doesn't exist" which is correct, but what I was hoping it that it would recreate the table.

like image 675
Prometheus Avatar asked Nov 03 '14 11:11

Prometheus


3 Answers

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.

like image 162
J.Q Avatar answered Nov 14 '22 13:11

J.Q


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!

like image 33
Raúl EL Avatar answered Nov 14 '22 12:11

Raúl EL


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, models

class 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

like image 22
yuvi Avatar answered Nov 14 '22 12:11

yuvi