#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: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Jacob Walls):
* needs_better_patch: 1 => 0
* needs_tests: 1 => 0
Comment:
On the PR Mariusz demonstrated several examples having to do with this
ticket's description where the error messages are sufficiently
informative. However, I think my test case is related to the original
poster's scenario (although it is hard to be certain), and shows Django
raising an improvable `NodeNotFoundError`.
Glad to give it another look, though, if you think I'm misreading the
original poster's use case. (To that end, Julian, I would be grateful if
you would be able to take a look at my suggested patch.)
--
Ticket URL: <https://code.djangoproject.com/ticket/29063#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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/073.fa769929938c4893ff3f6930c655a979%40djangoproject.com.
