I'm using Django 1.8.4. As my project is still under construction, I frequently remove all migration scripts, and rerun makemigrations to generate the initial migration scripts.
I found makemigrations would generate two migration scripts for one of my apps while other apps just have 0001_initial.py. It would be something like:
- 0001_initial.py
- 0002_auto_20150919_1645.py
I checked the content of 0002_auto_20150919_1645.py, it was adding foreign field from the other app's model.
I guess it might be related to the order of creating migrations for apps. So I delete these two migration scripts of this app and then run makemigrations again. Now I have only one migration script for this app.
My questions is:
Is there any way I can control the order makemigrations create migrations for apps?
For example, I have two apps, app1 and app2, and app1 depends on app2. Is it possible makemigrations create migration for app2 first, and then app1?
You can manually run migrations for an individual app.
./manage.py makemigrations app2
./manage.py makemigrations app1
./manage.py makemigrations # migrate the rest of your apps
You could also squash your existing migrations.
Related
Given any standard Django models.py file, how can you tell Django to include / exclude certain models conditionally (e.g. based on variables in the settings.py module) when running python manage.py makemigrations [app_name]?
When running python manage.py makemigrations [app_name] you cannot exclude certain models. You can write migrations manually, read the documentation: Writing database migrations.
Or run python manage.py makemigrations [app_name] and then edit the generated migrations file to delete operations that construct models you want to exclude.
i am new to django developement after making changes to my model i tried to run the command python manage.py makemigrations my_app
it detects changes in my model and shows me the message
todoapp/migrations/0001_initial.py
- Create model confess
- Create model UserChoice
- Create model comment
but on executing python manage.py migrate my_appcommand i've got this message
No migrations to apply.
i usually do this after making changes in models, i don't know what happened now.
plss help me.
Firstly, try
python manage.py makemigrations my_app
python manage.py migrate
If this does not work and the project is still in development:
Delete migrations folder and pycache folder.
Delete db.sqlite3 (your database).
Make and apply migrations again.
I think this will work.
Delete all migrations files and __pychache__except__init__.py from your project and app. Also db.sqlite3 database then rerun makemigrations and migrate commands. It should solve your issue.
I am trying to make two tenants with separate apps and models, the migrate_schemas make migrations for all the apps so need to separate the migrations is it possible
Use python manage.py makemigrations <app_name> and python manage.py migrate <app_name> for separate app migrations.
Suppose, we have a db's backup and a django program. The program do not have any migrations. First we restore db, that has created table and data. Now we want to make migrations from available db. Is it possible or not?
Yes, Django has the inspectdb method, which is described here.
But if the Django app already has the models defined that correspond to the backed up database, then you can just run makemigrations (follow #Shafikur's instructions).
Just go to your corresponding database terminals and delete all the records from you django_migrations table with
delete from django_migrations;
Go to terminal and run remove all files in migrations folder with
rm -rf <app>/migrations/
Reset all the migrations of the Django's built-in apps like admin with the command
python manage.py migrate --fake
Create initial migrations for each and every app:
python manage.py makemigrations <app>
To create initial fake migrations just run
python manage.py migrate --fake-initial
If I make a change to a model in django it no longer picks up changes with
python manage.py makemigrations
I did previously delete the database (postgres) via dropdb, and recreated it with createdb. I then deleted the migrations from the apps migrations folder. Before doing this makemigrations did work ok for that app.
What is the best way to fix?
Recreate the migrations folder with an __init__.py file. A shortcut for this is to run python manage.py makemigrations <app_label>. The app label here is important, otherwise it will treat your app as an unmigrated app and it won't create any migrations.
Try this:
python manage.py makemigrations app_name
Or, just add __init__.py file on each migrations folder.