#26384: Migrations crash renaming the pk of a model with a self-referential
foreign
key
---------------------------------+------------------------------------
Reporter: brian | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: 1.9
Severity: Release blocker | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
---------------------------------+------------------------------------
Comment (by timgraham):
I think the MySQL issue is #24995 ("MySQL error when renaming a primary
key"). There is a patch there but I closed the PR because the test didn't
act as a regression test for me. Now I see that maybe I needed to test
with an older MySQL. The patch there still doesn't solve the issue but it
changes the exception on the test added in this ticket to something within
Django `AttributeError: 'AutoField' object has no attribute 'model'`
instead of something from `MySQL: OperationalError: (1025, "Error on
rename of './test_django/#sql-58c_94' to './test_django/schema_node'
(errno: 150)")`. I think we can continue the discussion on that ticket.
--
Ticket URL: <https://code.djangoproject.com/ticket/26384#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/063.aea8f0659747a0df4c6ba8b0978651dd%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
