#24995: MySQL error in migrations
-------------------------------+--------------------------------
Reporter: EikeDehling | Owner: nobody
Type: Uncategorized | Status: new
Component: Migrations | Version: 1.8
Severity: Normal | Keywords: rename mysql error
Triage Stage: Unreviewed | Has patch: 1
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------
In a migration where a primary-key field is renamed, a mysql error occurs,
because mysql needs foreign keys to be disabled/dropped for that
operation.
See here for an example of the error you would get:
http://stackoverflow.com/questions/4080611/1025-error-on-rename-of-
database-sql-2e0f-1254ba7-to-database-table
I have a patch which fixes the issue:
https://github.com/EikeDehling/django/commit/dbe0c4692fe1a7d73e4de345a171b8cbb35651b2
Please let me know what i can do to get this merged/fixed in django.
--
Ticket URL: <https://code.djangoproject.com/ticket/24995>
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/054.95da81f9b9b8d704839775c6afb8d15e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
