#25154: Migration errors don't contain enough information to debug properly
------------------------------+--------------------------------------
Reporter: brandonmoser | Owner: nobody
Type: New feature | Status: new
Component: Migrations | Version: 1.7
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 shaib):
I agree that migration stacktraces are missing references to the
migrations which caused them. Perhaps it can be helpful to add debugging
hints for migrations, e.g. "increase verbosity so you can tell which
migration caused the problem".
--
Ticket URL: <https://code.djangoproject.com/ticket/25154#comment:4>
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/070.f3f15c376a948ff9ea6824b2510b09ba%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
