CODEWITHSUNDEEP
djangomigration
JulienD
JulienD

Reputation: 7293

Django makemigrations wants to delete everything it just created

I just followed this procedure:

At this point Django says I have "changes that are not yet reflected in a migration, and so won't be applied. Run 'manage.py makemigrations' to make new migrations, and then re-run 'manage.py migrate' to apply them"

But when I run makemigrations, it creates a new one that wants to "Remove field" every foreign key and "Delete model" all of my models. If I run it it empties my database. My models.py are intact.

What is happening ??

Upvotes: 4

Views: 1806

Answers (2)

Carl Marshall
Carl Marshall

Reputation: 349

I've just had the same errors, but I hit the makemigrations building a migration full of Remove Field and Delete Model commands before I tried the migrate command.

In my case, the solution was related this being an old project I was resurrecting, and it had a number of Model.Meta.app_name values set, as well as entries in apps.py for each project. These were now in conflict with the way settings was interpreting the project, and even though my models were imported into views and admin, they weren't being seen by the migration code. Deleting these app_name tags on the models, and modifying the AppConfig name in apps.py solved this, so that the running makemigrations again caused the expected changes (alter field, etc), and all was fine.

I didn't find any other questions or answers that quite matched this one and my experience, so I hope if anyone else looks for this, they'll find it here like I did ;-)

Upvotes: 0

A. Grinenko
A. Grinenko

Reputation: 331

I had the same problem in my project. Running forward I can say that django removes models that has no import (making the Delete model migration). The documentation says that you should import your model in the myApp/models/__init__.py file (see https://docs.djangoproject.com/en/1.11/topics/db/models/#organizing-models-in-a-package).

In my case I imported the model somewhere to make manipulations but model had been removing elsewhere.

I had made a useless import in an admin.py file that has solved my situation (I didn't try to follow the documentation and import it in the __init__.py but sure it should help). I had not realized yet why does it work that way (hope that someone could note this moment) and also hope this solution will help you.

Upvotes: 5

Related Questions