Opened 10 years ago

Last modified 10 years ago

#23331 closed Bug

Circular dependencies are not resolved by new Migrate framework — at Version 1

Reported by: Aidan Lister Owned by: Andrew Godwin
Component: Migrations Version: dev
Severity: Normal Keywords: migrate
Cc: aidan@…, Markus Holtermann Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description (last modified by Aidan Lister)

It's very easy and not explicitly not-supported to create circular dependencies in your apps. I have attached a test project which has two circular dependency resolution failures.

This fails to create migrations:

./manage.py makemigrations contractors inspections organisations properties reports tasks timeline

This creates the migrations:

./manage.py makemigrations properties reports tasks timeline
./manage.py makemigrations contractors inspections

But then ./manage.py migrate fails:

django.db.migrations.graph.CircularDependencyError: [('contractors', u'0002_auto_20140821_0156'), ('reports', u'0001_initial'), ('inspections', u'0001_initial'), ('contractors', u'0002_auto_20140821_0156')]

I have tried manually breaking up the migrations into lots of little steps, but you'll have the same problem with the reports and inspections app. Even with lots of tiny migrations it eventually loops around.

Change History (2)

by Aidan Lister, 10 years ago

Attachment: testproject.zip added

comment:1 by Aidan Lister, 10 years ago

Description: modified (diff)
Note: See TracTickets for help on using tickets.
Back to Top