#29063: Replacement Migrations not being executed because of unapplied
migrations
should raise a warning.
-------------------------------------+-------------------------------------
Reporter: Julian | Owner: Jacob
Type: | Walls
Cleanup/optimization | Status: assigned
Component: Migrations | Version: 1.9
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 Jacob Walls):
* owner: nobody => Jacob Walls
* status: new => assigned
Comment:
Somewhat similar to #23556, I think we can raise a more informative
`NodeNotFoundError`. Should have a patch soon, just need to toy with
whether backward migrations are also a problem.
--
Ticket URL: <https://code.djangoproject.com/ticket/29063#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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/073.6302837ce9f8d6f3cab537f82a108b68%40djangoproject.com.
