#25154: Add tips on debugging migration failures
-------------------------------+------------------------------------
Reporter: brandonmoser | Owner: nobody
Type: New feature | Status: new
Component: Documentation | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 1 | UI/UX: 0
-------------------------------+------------------------------------
Comment (by MarkusH):
I've a patch laying around to output the exact operation and migration
that failed. Only struggling with the connection resets when a migration
failed, but that shouldn't be a problem to fix. Will push and link when
I've decent WiFi to rebase onto current master.
--
Ticket URL: <https://code.djangoproject.com/ticket/25154#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 [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.fd81e7ff1eae7f24108c7fc58ce4cba7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
