#22874: Swappable dependency breaks if swappable model not in first migration of
its app
---------------------------------+------------------------------------
Reporter: melinath | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: master
Severity: Release blocker | 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 andrewgodwin):
One of the caveats we had to do to be able to support swappable models was
that they MUST be in the first migration of their respective app (as
you've seen, otherwise dependency problems occur). There's literally no
way to fix this, as it's logically impossible to construct a dependency
graph otherwise with our model.
I'll add documentation highlighting this next to the existing warning
about dependencies from unmigrated apps.
--
Ticket URL: <https://code.djangoproject.com/ticket/22874#comment:6>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.45941615aa64cf621c43d18ba90a6f07%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
