#28305: AlterField migration tries to alter column that still has a foreign key
contraint
-------------------------------------+-------------------------------------
Reporter: Andreas Backx | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: master
Severity: Normal | Resolution:
Keywords: mysql, | Triage Stage:
onetoonefield, utf8mb4, foreign | Unreviewed
key |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Andreas Backx):
I'll try to create a test for the Django's test suite hopefully this week
and bisect it that way as something came up that needs to prioritisation
here. Should I add the failing test in the first commit and add a patch in
the second commit of the PR?
--
Ticket URL: <https://code.djangoproject.com/ticket/28305#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 post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/070.9791ba6ebe16a7d02c38a5cb944c930f%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
