#28305: AlterField migration tries to alter column that still has a foreign key
contraint
-------------------------------------+-------------------------------------
Reporter: Andreas Backx | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: master
Severity: Release blocker | Resolution: fixed
Keywords: mysql, | Triage Stage: Accepted
onetoonefield, utf8mb4, foreign |
key |
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim Graham <timograham@…>):
In [changeset:"4dc35e126d8461589b4b4bc47b6f6bd6cc4a1455" 4dc35e12]:
{{{
#!CommitTicketReference repository=""
revision="4dc35e126d8461589b4b4bc47b6f6bd6cc4a1455"
[2.0.x] Fixed #28305 -- Fixed "Cannot change column 'x': used in a foreign
key constraint" crash on MySQL with a sequence of AlterField or
RenameField operations.
Regression in 45ded053b1f4320284aa5dac63052f6d1baefea9.
Backport of c3e0adcad8d8ba94b33cabd137056166ed36dae0 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/28305#comment:14>
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.1a401eb290d88c8f5c1703c8141c8e71%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
