#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 Mariusz Felisiak <felisiak.mariusz@…>):
In [changeset:"f5ede1cb6da473166d22c04dcbd8240e2a0f223d" f5ede1cb]:
{{{
#!CommitTicketReference repository=""
revision="f5ede1cb6da473166d22c04dcbd8240e2a0f223d"
Refs #28305 -- Consolidated field referencing detection in migrations.
This moves all the field referencing resolution methods to shared
functions instead of duplicating efforts amongst state_forwards and
references methods.
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/28305#comment:17>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/070.e2a054bf0ca53221e2b9e7f1c24b9396%40djangoproject.com.
