#26609: Spurious migrations caused by non-deteministic field choices order
-------------------------------------+-------------------------------------
Reporter: Harry Percival | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Database layer | Version: dev
(models, ORM) |
Severity: Normal | Resolution:
Keywords: migrations | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Natalia Bidart):
* resolution: wontfix =>
* stage: Unreviewed => Accepted
* status: closed => new
* type: Bug => Cleanup/optimization
* version: 1.9 => dev
Comment:
Based on conversations in #35854, we are repurposing and reopening this
ticket to grow the choices existing system check to advice against
unorderable iterables.
--
Ticket URL: <https://code.djangoproject.com/ticket/26609#comment:5>
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/01070192b95327a3-da95b52a-c435-4111-bdb0-3709ea3451f6-000000%40eu-central-1.amazonses.com.
