#24572: Migration plan may be broken when applying migrations on a clean
database
----------------------------+------------------------------------
Reporter: MarkusH | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: master
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
----------------------------+------------------------------------
Changes (by knbk):
* stage: Unreviewed => Accepted
Comment:
There's more to this than just the fact that a.2 requires b.3 but b.3 is
not a dependency of a.2. Even if a.2 exists but is not run, the above
error will be thrown when migrating to b.2. Git bisect shows that this
particular error is a regression from
1aa3e09c2043c88a760e8b73fb95dc8f1ffef50e.
Fixing the regressions from that commit at least opens up an easy
workaround that doesn't involve deleting migration files. A simple
`manage.py migrate b` followed by `manage.py migrate a` will work.
--
Ticket URL: <https://code.djangoproject.com/ticket/24572#comment:2>
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/065.c91d22c0ec4c4fbdfd85fe0f62bc9a32%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
