#30276: reverse DeleteModel migration with a primary key OneToOneField fails in
MySQL
------------------------------------+--------------------------------------
Reporter: Florian Zimmermann | Owner: nobody
Type: Bug | Status: closed
Component: Migrations | Version: 2.1
Severity: Normal | Resolution: fixed
Keywords: migrations, mysql | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
------------------------------------+--------------------------------------
Changes (by Tim Graham):
* status: new => closed
* type: Uncategorized => Bug
* resolution: => fixed
Comment:
This is fixed in the upcoming Django 2.2 release by
ad82900ad94ed4bbad050b9993373dafbe66b610. The second migration doesn't
have a `RemoveField` operation.
--
Ticket URL: <https://code.djangoproject.com/ticket/30276#comment:1>
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/067.a8edc095bed9c9c463f698b40a075ce7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
