#28351: "Conflicting migrations detected" CommandError due to replacement
Migration
being removed
-------------------------------+--------------------------------------
Reporter: Daniel Hahler | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.11
Severity: Normal | Resolution:
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Comment (by Daniel Hahler):
Not currently.
I think a fix might be to move over the `replaces` from the node that gets
replaced, and/or only to replace up to the parent that got applied in
https://github.com/django/django/blob/a6756195c1a11eee10c16c96fe95d52e22e1d9ba/django/db/migrations/graph.py#L243-L245.
--
Ticket URL: <https://code.djangoproject.com/ticket/28351#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.923b5748d5d5871cc6f7ab862d6e843b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
