#23790: Possible bad interaction between migration dependencies and relabeling
apps
----------------------------+------------------------------------
Reporter: aaugustin | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.7
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 carljm):
To me this seems like a straightforward case of "not every edge case can
be automatic." The fix is manual, but simple, right? You just have to
replace that app label in all existing migrations that reference it.
--
Ticket URL: <https://code.djangoproject.com/ticket/23790#comment:5>
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/067.16e915b998728b2f75b63c99f0e7105f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
