#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 shaib):
I finally figured out what's going on here, and why it was hard to
reproduce. The issue is actually within our control and can be solved once
and for all; then we'll be able to remove the
`connection_persists_old_columns` database feature. See #24200.
--
Ticket URL: <https://code.djangoproject.com/ticket/24163#comment:18>
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.ab9334e92506660cdfb338ecd1a5dc53%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
