#24163: Migrations fail when changing from OneToOneField to ForeignKey
-------------------------------------+-------------------------------------
Reporter: harnash | Owner: MarkusH
Type: Bug | Status: closed
Component: Migrations | Version: 1.7
Severity: Normal | Resolution: fixed
Keywords: OneToOneField | Triage Stage: Ready for
ForeignKey MySQL | checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Markus Holtermann <info@…>):
In [changeset:"db2a97870d74bc689428d9c2a942115ef799f2d2"]:
{{{
#!CommitTicketReference repository=""
revision="db2a97870d74bc689428d9c2a942115ef799f2d2"
[1.7.x] Fixed #24163 -- Removed unique constraint after index on MySQL
Thanks Łukasz Harasimowicz for the report.
Backport of 5792e6a88c1444d4ec84abe62077338ad3765b80 from master
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/24163#comment:7>
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/065.353decc411bd2fb425516cfe5ed4e2ad%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
