#26609: Spurious migrations caused by non-deteministic field choices order
-------------------------------------+-------------------------------------
Reporter: hjwp | Owner: nobody
Type: Bug | Status: closed
Component: Database layer | Version: 1.9
(models, ORM) |
Severity: Normal | Resolution: wontfix
Keywords: migrations | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by charettes):
* status: new => closed
* resolution: => wontfix
Comment:
I'm afraid there's not much we can do about it.
The `choices` option is meant to be ordered and the migration framework
correctly detects changes in ordering.
--
Ticket URL: <https://code.djangoproject.com/ticket/26609#comment:3>
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/062.2a4a0c2410c1ab74e4da1af6dea48032%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
