#23337: CircularDependencyError when squashing migrations
----------------------------+------------------------------------
Reporter: no | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: dev
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+------------------------------------
Comment (by Gordon Wrigley):
We have adopted a (rather complex) process to produce dual level squashes.
The guts of the idea is instead of squashing each app to a single
migration we squash to two migrations. The first one creates all the
tables, the second one creates all the FK's. This resolves all circularity
issues.
--
Ticket URL: <https://code.djangoproject.com/ticket/23337#comment:18>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/010701934f57cc42-0ed2f822-afae-4b59-85ae-0205fe494618-000000%40eu-central-1.amazonses.com.
