Django keeps making duplicate migrations in for my application. I've ran makemigrations and migrate before I changed my model. After the changes I ran makemigrations again to make migrations for the updated model, I got the following error:
CommandError: Conflicting migrations detected; multiple leaf nodes in the migration graph: (0001_initial, 0001_initial 3 in sessions; 0002_remove_content_type_name 3, 0002_remove_content_type_name, 0001_initial 3 in contenttypes; 0002_alter_permission_name_max_length 3, 0010_alter_group_name_max_length 3, 0007_alter_validators_add_error_messages 3, 0006_require_contenttypes_0002 3, 0005_alter_user_last_login_null 3, 0001_initial 3, 0008_alter_user_username_max_length 3, 0009_alter_user_last_name_max_length 3, 0011_update_proxy_permissions, 0011_update_proxy_permissions 3, 0004_alter_user_username_opts 3, 0003_alter_user_email_max_length 3 in auth; 0003_logentry_add_action_flag_choices 3, 0002_logentry_remove_auto_add 3, 0003_logentry_add_action_flag_choices, 0001_initial 3 in admin).
To fix them run 'python manage.py makemigrations --merge'
Running makemigrations --merge doesn't work: ValueError: Could not find common ancestor of {'0002_remove_content_type_name', '0002_remove_content_type_name 3', '0001_initial 3'}
There are many duplicate migrations in apps that I haven't touched (auth, admin, etc.):
admin
[ ] 0001_initial 3
[X] 0001_initial
[ ] 0002_logentry_remove_auto_add 3
[X] 0002_logentry_remove_auto_add
[X] 0003_logentry_add_action_flag_choices
[ ] 0003_logentry_add_action_flag_choices 3
auth
[ ] 0001_initial 3
[X] 0001_initial
[ ] 0002_alter_permission_name_max_length 3
[X] 0002_alter_permission_name_max_length
[ ] 0003_alter_user_email_max_length 3
[X] 0003_alter_user_email_max_length
[ ] 0004_alter_user_username_opts 3
[X] 0004_alter_user_username_opts
[ ] 0005_alter_user_last_login_null 3
[X] 0005_alter_user_last_login_null
[ ] 0006_require_contenttypes_0002 3
[X] 0006_require_contenttypes_0002
[ ] 0007_alter_validators_add_error_messages 3
[X] 0007_alter_validators_add_error_messages
[ ] 0008_alter_user_username_max_length 3
[X] 0008_alter_user_username_max_length
[ ] 0009_alter_user_last_name_max_length 3
[X] 0009_alter_user_last_name_max_length
[ ] 0010_alter_group_name_max_length 3
[X] 0010_alter_group_name_max_length
[X] 0011_update_proxy_permissions
[ ] 0011_update_proxy_permissions 3
contenttypes
[ ] 0001_initial 3
[X] 0001_initial
[X] 0002_remove_content_type_name
[ ] 0002_remove_content_type_name 3
database
(no migrations)
sessions
[X] 0001_initial
[ ] 0001_initial 3
The only app that, as far as I know, should've been affected is database. Why is Django making these duplicate migrations? Is there any way I can get rid of these? Or apply them so they are not blocking anymore? How I can make sure this doesn't happen again?
Sometimes, if you have the option, the easiest and fastest way is...
Delete migration files.
Delete entire database.
run "python manage.py makemigrations" again
run "python manage.py migrate" again
or... if you have a db in production with data and you can't reset:
Check last production version
Delete migration files (until this version).
Delete entire local(sqlite) database.
run "python manage.py makemigrations" again
run "python manage.py migrate" again
Important... copy /migrations/ folder somewhere to recover files if necessary.
It turned out the duplicates weren't created by Django but by some other process. Completely removing my environment and reinstalling all dependencies helped. Removing the migrations also would've worked.
Related
I have a django project, and I wish to update a MySQL database from a previous version of the codebase to be compatible with the current version.
I have all of the migrations for the project, but I do not know which was the last one applied to this alternate database.
I can try and determine this manually, but I was wondering if there was an easier automated way of finding which the first unapplied migration is.
You can work with the showmigrations command [Django-doc], this will generate a list of the migrations where it will check a box in case that migration has been applied, so:
python3 manage.py showmigrations
or for a specific app:
python3 manage.py showmigrations app_name
For example for auth, a possible result is:
$ python manage.py showmigrations auth
auth
[X] 0001_initial
[X] 0002_alter_permission_name_max_length
[X] 0003_alter_user_email_max_length
[X] 0004_alter_user_username_opts
[X] 0005_alter_user_last_login_null
[X] 0006_require_contenttypes_0002
[X] 0007_alter_validators_add_error_messages
[X] 0008_alter_user_username_max_length
[X] 0009_alter_user_last_name_max_length
[X] 0010_alter_group_name_max_length
[ ] 0011_update_proxy_permissions
[ ] 0012_alter_user_first_name_max_length
This thus means that all migrations have been applied, except the last two.
showmigrations shows that there is 31 available migrations:
# python3 manage.py showmigrations
admin
[X] 0001_initial
[X] 0002_auto_20190114_1409
[X] 0003_auto_20190114_1410
auth
[X] 0001_initial
[X] 0002_alter_permission_name_max_length
[X] 0003_alter_user_email_max_length
[X] 0004_alter_user_username_opts
[X] 0005_alter_user_last_login_null
[X] 0006_require_contenttypes_0002
[X] 0007_auto_20190114_1409
authtoken
[X] 0001_initial
[X] 0002_auto_20160226_1747
[X] 0003_auto_20190114_1409
contenttypes
[X] 0001_initial
[X] 0002_remove_content_type_name
[X] 0003_auto_20190114_1409
exchange_delivery
[X] 0001_initial
[X] 0002_enlarge_phone_field
[X] 0003_unique_external_id
[X] 0004_add_warehouse
[X] 0005_add_delivery_point_type
[X] 0006_update_delivery_type_operating_mode
[X] 0007_add_delivery_point_region_model
[X] 0008_update_warehouse_exchange
[X] 0009_add_verbose_name_for_warehouse_and_add_delivery_point_banned_group
[X] 0010_add_active_flag_to_warehouse
[X] 0011_auto_20190114_1409
sessions
[X] 0001_initial
[X] 0002_auto_20190114_1410
volt
[X] 0001_initial
[X] 0002_auto_20190114_1410
How to apply all this migrations ? migrate shows that No migrations to apply
# python3 manage.py migrate
Operations to perform:
Synchronize unmigrated apps: corsheaders, export, opinion, volt.integration1c.delivery, custom_logger, event_listener, legacy, region, order, catalog, promo_table, messages, staticfiles, api, best_product, shop, general, market_cpa, rest_framework, delivery, exchange, talk
Apply all migrations: auth, authtoken, sessions, exchange_delivery, admin, volt, contenttypes
Synchronizing apps without migrations:
Creating tables...
Running deferred SQL...
Installing custom SQL...
/usr/lib/python3.6/site-packages/django/core/management/commands/loaddata.py:239: RemovedInDjango19Warning: initial_data fixtures are deprecated. Use data migrations instead.
RemovedInDjango19Warning
Installed 0 object(s) (of 6) from 1 fixture(s)
Running migrations:
No migrations to apply.
I'm not familiar with Django, I need just dockerize existing app.
As far as I understand from output of python3 manage.py syncdb command
django.db.utils.ProgrammingError: (1146, "Table '220-django.auth_user' doesn't exist")
Problem is that initial migrations for django and django-admin are not applied
Project is under Django 1.8.14
As I can see, all the migrations has [X] beside their names. Means these migrations are already applied, as per documentation. If there is any un-applied migrations, then it will show up as [ ] beside the name of the migration. For more details(if the migrations has been applied or not), please check the django_migrations table in DB.
You have some entries in django_migrations table in your database so that migrate shows No migrations to apply.
To solve this, goto database console and run the following command
delete from django_migrations;
Or, directly go to the database table and delete all rows.
Then run
python manage.py migrate
I have been struggling with this aggravation for a little bit, and I have not been able to find a definitive answer elsewhere online.
I have a Django app that uses multiple databases; a default db and then a client db. The default db holds universal tables. The client db holds custom data/tables created by the client who uses my application.
I understand how migrations work, but I am using 2 databases that should not have the same models included when I run migrations. client's should have the client tables and the default db should hold the universal data.
It is also important to note (because of the question below) that I do not make application specific models (other than the default ones auto-generated by Django itself), I use 2 packages/applications for this: objects and objects_client, objects holds the default db models and objects_client holds the client db models.
client_db is also the name I use in settings.py
Now here is my issue:
I know I can run python3 manage.py migrate objects_client --database=client_db and python3 manage.py migrate objects --database=default, but I don't want to have to individually specify the admin, auth, contenttypes, and sessions migrations to the default database so I also run, python3 manage.py migrate, which obviously places objects_client in the default DB as well (which I don't want).
How do I go about runing the a version of the default python3 manage.py migrate command with an exclusion of an app, i.e. objects_client, without changing each model in that app to managed=false (because that is a pain)?
Here is the output of showmigrations if it helps decribe what I mean in more detail, these are the apps being migrated.
admin
[X] 0001_initial
[X] 0002_logentry_remove_auto_add
[X] 0003_logentry_add_action_flag_choices
auth
[X] 0001_initial
[X] 0002_alter_permission_name_max_length
[X] 0003_alter_user_email_max_length
[X] 0004_alter_user_username_opts
[X] 0005_alter_user_last_login_null
[X] 0006_require_contenttypes_0002
[X] 0007_alter_validators_add_error_messages
[X] 0008_alter_user_username_max_length
[X] 0009_alter_user_last_name_max_length
contenttypes
[X] 0001_initial
[X] 0002_remove_content_type_name
objects
[X] 0001_initial
objects_client
[X] 0001_initial
sessions
[X] 0001_initial
Set up a database routing scheme with Database routers and provide an allow_migrate method to determine if the migration operation is allowed to run on the database with alias db.
class Router:
...
def allow_migrate(self, db, app_label, model_name=None, **hints):
"""
Make sure the objects_client app only appears in the 'client_db'
database.
"""
if app_label == 'objects_client':
return db == 'client_db'
return None
Finally, in the settings.py file, add the following
DATABASE_ROUTERS = ['path.to.Router']
now im trying to migrate empty django project.
when enter this command
python manage.py showmagrations
result is
admin
[ ] 0001_initial
[ ] 0002_logentry_remove_auto_add
[ ] 0003_logentry_add_action_flag_choices
auth
[ ] 0001_initial
[ ] 0002_alter_permission_name_max_length
[ ] 0003_alter_user_email_max_length
[ ] 0004_alter_user_username_opts
[ ] 0005_alter_user_last_login_null
[ ] 0006_require_contenttypes_0002
[ ] 0007_alter_validators_add_error_messages
[ ] 0008_alter_user_username_max_length
[ ] 0009_alter_user_last_name_max_length
contenttypes
[ ] 0001_initial
[ ] 0002_remove_content_type_name
myapp
[ ] 0001_initial
sessions
[ ] 0001_initial
is this situation how can i migrate all of 0001_initial?
or how can i run spesific migrtaion step?
ex) admin 0001_initial only
it's simple you have only put the app name and the migration you want to migrate
if you want to migrate the inital of the admin app:
$ python manage.py migrate admin 0001_initial
NOTE: it will unapply the later migrations
I am working on a Django(1.8) project.
I am trying to implement django-seo2.
Integrated Travis CI on GitHub for continuous integration.
I keep getting the following error on Travis:
ProgrammingError: relation "django_content_type" does not exist
On my local machine:
python manage.py showmigrations
account
[ ] 0001_initial
[ ] 0002_email_max_length
admin
[ ] 0001_initial
auth
[ ] 0001_initial
[ ] 0002_alter_permission_name_max_length
[ ] 0003_alter_user_email_max_length
[ ] 0004_alter_user_username_opts
[ ] 0005_alter_user_last_login_null
[ ] 0006_require_contenttypes_0002
authtoken
[ ] 0001_initial
[ ] 0002_auto_20160226_1747
contenttypes
[ ] 0001_initial
[ ] 0002_remove_content_type_name
payment
[ ] 0001_initial
profiles
[ ] 0001_initial
[ ] 0002_auto_20160610_1309
sessions
[ ] 0001_initial
sites
[ ] 0001_initial
socialaccount
[ ] 0001_initial
[ ] 0002_token_max_lengths
[ ] 0003_extra_data_default_dict
webpages
(no migrations)
If I migrate before implementing django-seo2 and then I migrate after implementing django-seo2 no error occurs.
But if new database is used and after implementing django-seo2, I try python manage.py migrate , the same error occurs:
django.db.utils.ProgrammingError: relation "django_content_type" does not exist
The version on pypi is 12 commits behind master.
I solved the problem by installing the django-seo2 directly from its source on github
I created an issue for update in django-seo2 Python Package Index, but I think the github repository is not maintained by the owner now.