#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: Release blocker | Resolution:
Keywords: mysql, | Triage Stage: Accepted
onetoonefield, utf8mb4, foreign |
key |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Tim Graham):
Markus, do you have any suggestions about how to fix this? I confirmed
that reverting the
[https://github.com/django/django/commit/45ded053b1f4320284aa5dac63052f6d1baefea9
#diff-efb7d00c2383393046c9c5d842f45499R201 delayed rendering changes] to
`AlterField` fixes it. Maybe the reloading shouldn't be delayed if a field
is pointed to by a foreign key? (i.e. reloading should be delayed for both
forward and reverse relations)
--
Ticket URL: <https://code.djangoproject.com/ticket/28305#comment:11>
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.e255f722c22de9e481a7e0903d767c8a%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
