#24653: Migrations: Removing a field with foreign key constraint fails
-------------------------------------+-------------------------------------
Reporter: karolyi | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.8
Severity: Normal | Resolution:
Keywords: foreign key | Triage Stage:
constraint mysql | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by timgraham):
Which MySQL version and storage engine are you using? I tried to reproduce
using the tutorial by removing the `question =
models.ForeignKey(Question)` field. Can you reproduce using that method?
Tested with MySQL 5.6.19 and both InnoDB and MyISAM storage engines;
Django master and stable/1.8.x branches.
--
Ticket URL: <https://code.djangoproject.com/ticket/24653#comment:4>
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/065.d02149451b51bd294eb066b8fa0a6c5e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
