#29063: Replacement Migrations not being executed because of unapplied
migrations
should raise a warning.
----------------------------+---------------------------------------
Reporter: Julian | Owner: Jacob Walls
Type: Bug | Status: assigned
Component: Migrations | Version: 1.9
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+---------------------------------------
Changes (by Jacob Walls):
* type: Cleanup/optimization => Bug
Comment:
After Mariusz helpfully enumerated scenarios where the current messaging
is sufficient, we found really only a single case with an improvable
`NodeNotFoundError`, and I agree it would be better to just fix the
failure point than invest energy in a patch changing the exception
message:
[https://github.com/django/django/pull/14727 New PR]
--
Ticket URL: <https://code.djangoproject.com/ticket/29063#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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/073.a02bb14d31f4a2218d27632722a708ef%40djangoproject.com.
