#29854: Altering the primary key targeted by several foreign keys incorrectly
alters the foreign key's NULL attribute
-------------------------------------+-------------------------------------
Reporter: Rick Yang | Owner: nobody
Type: Bug | Status: new
Component: Migrations | Version: master
Severity: Normal | Resolution:
Keywords: MySQL, Migration, | Triage Stage: Accepted
Altering primary key, |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Sanskar Jaiswal):
Hi I would like to work on this issue, and was hoping to get some doubts
cleared, before I start ;)
Replying to [comment:7 Baptiste Mispelon]:
> You can probably start to see where the problem is coming from:
`get_fields()` doesn't seem to guarantee a deterministic order of the
returned fields, which leads to old fields and new fields being mismatched
in some cases.
What does it mean when you say, that "`get_fields()` doesn't guarantee a
deterministic order of the returned fields"?
Thanks!
--
Ticket URL: <https://code.djangoproject.com/ticket/29854#comment:8>
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 view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.3c23af7b1097ffa43cf7384ed728db0e%40djangoproject.com.
