Django 1.8: Create initial migrations for existing schema

问题

I started a django 1.8 project, which uses the migrations system.
Somehow along the way things got messy, so I erased the migrations folders and table from the DB, and now I\'m trying to reconstruct them, with no success.

I have three apps (3 models.py files), and the models reflect the tables EXACTLY!

The best approach that I\'ve found so far was:

1. Erase all migrations folders. Done!
2. Delete everything from the django_migrations table. Done!
3. Run python manage.py makemigrations --empty <app> for every app. Done!
4. Run python manage.py migrate --fake. Done! (although it works only if I run it after every makemigrations command.

Now I add a new field, run the makemigrations command, and I receive the following error:
django.db.utils.OperationalError: (1054, \"Unknown column \'accounts_plan.max_item_size\' in \'field list\'\")

I\'ve been burning HOURS on this thing. How the h**l can I initialize the migrations so I can continue working without migration interruptions every time?

Why is it so complicated? Why isn\'t there a simple one-liner: initiate_migrations_from_schema?

EDIT:
Now things get even nastier. I truncated the django_migrations table and deleted all the migrations folder.
Now I try to run python manage.py migrate --fake-initial (something I found in the DEV docs), just so it sets up all of Django\'s \'internal\' apps (auth, session, etc) and I\'m getting:
(1054, \"Unknown column \'name\' in \'django_content_type\'\").
Now, this \"column\" is not a real column. It\'s a @property defined in Django\'s contenttypes app. WHAT IS GOING ON HERE? Why is it identifying the name property as a real column?

回答1:

Finally got it to work, although I don't know why and I hope it will work in the future.
After doing numerous trials and going through Django's dev site (link).
Here are the steps (for whoever runs into this problem):

1. Empty the django_migrations table: delete from django_migrations;
2. For every app, delete its migrations folder: rm -rf <app>/migrations/
3. Reset the migrations for the "built-in" apps: python manage.py migrate --fake
4. For each app run: python manage.py makemigrations <app>. Take care of dependencies (models with ForeignKey's should run after their parent model).
5. Finally: python manage.py migrate --fake-initial

After that I ran the last command without the --fake-initial flag, just to make sure.

Now everything works and I can use the migrations system normally.

I'm sure I'm not the only one who encounters this issue. It must be documented better and even simplified.

Update for Django 1.9 users:
I had this scenario again with a Django 1.9.4, and step 5 failed.
All I had to do is replace --fake-initial with --fake to make it work.

回答2:

django ..., 1.8, 1.9, ...

What you want to achieve is squashing existing migrations and use replacement for them.

How to do it right without using any command when releasing (a case without impact on database and coworkers).

1. For every app, get rid of its migrations folder: mv <app>/migrations/ <app>/migrationsOLD/

2. For each that app run: python manage.py makemigrations <app>.

3. Customize each new migration:

   • if you have a complex app, or more apps and related models between them, to avoid CircularDependencyError or ValueError: Unhandled pending operations for models:

     prepare second empty migration in <app> 0002_initial2.py (put there dependency to app_other::0001_initial.py and <app>::0001_initial.py as well - all ForeignKey, M2M related to models created in 0001 migration step in other apps)

     All must be in order - sometimes it will require more migrations to prepare. Take care of dependencies attribute here in each Migration.

   • take care of initial values - verify yourself all RunPython actions from migrationsOLD and copy the code to new initial migration if needed.

   • (optional for --fake-initial) Add initial=True to all new Migration classes (0002 too if was added).

   • Add replaces attribute in new Migration class. (like own custom a squashmigrations). Put there all old migrations from <app>

4. Verify everything with makemigrations.

   assert "No changes detected"

5. Check if migrate -l show [x] everywhere

   assert similar:

   [X] 0001_initial

   [X] 0002_initial2 (102 squashed migrations)

Example:

For old:

0001_initial.py
0002_auto.py
...
0103_auto.py

prepare:

0001_initial.py
0002_initial2.py  (optional but sometimes required to satisfy dependency)

and add to replacesto last one (0002 here, can be 0001):

replaces = [(b'<app>', '0002_auto.py'), ..., (b'<app>', '0103_auto.py')]

0001_initial.py should be named the same way as old one.

0002_initial2.py is new one, but it's a replacement for old migrations so Django will treat it as loaded.

回答3:

I've run into this scenario but I've never had to drop the database to solve it. Typically I delete the migrations folder from the app's, and remove the migration entries from the database.

I would try to run make migrations one app at a time. If any of the app's rely upon other tables obviously add them last.

Also I usually just run, python manage.py makemigrations then just python manage.py migrate Even with the initial migration it should work fine with Django 1.7 and 1.8.

回答4:

If you are using routers, might be a problem there. Check method allow_migrate if it is executed in a right way in routers.py. Try to set return value always to be True, and check whether it resolves problem,

def allow_migrate(self, db, app_label, model_name=None, **hints):
    return True

来源：https://stackoverflow.com/questions/29888046/django-1-8-create-initial-migrations-for-existing-schema