#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 AlexHill):
Hi Claude,
Interesting...my best guess is that this is a separate problem exposed by
the test that was added in this patch, since the only code changes in the
patch were to the SQLite schema editor. The original report bears that
out:
> So to get this fail:
> * Use mysql (different error) OR
> * Use sqlite and Django >= 1.9 (error quoted above)
I don't have MySQL set up, but this will be useful:
http://stackoverflow.com/questions/1457305/mysql-creating-tables-with-
foreign-keys-giving-errno-150
That said, the pull request passed all the tests under all databases. How
could that have happened?
Cheers,
Alex
--
Ticket URL: <https://code.djangoproject.com/ticket/26384#comment:15>
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.bafd50a3e2093638f7334f0506e36a0e%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
