#35854: Order of "choices" on CharField randomly changing forcing new migrations
despite no changes.
----------------------------+--------------------------------------
Reporter: Karl | Owner: (none)
Type: Bug | Status: closed
Component: Migrations | Version: 5.1
Severity: Normal | Resolution: duplicate
Keywords: | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------+--------------------------------------
Comment (by Claude Paroz):
Replying to [comment:3 Natalia Bidart]:
> Do you see a concrete issue with using sets? (other than dropdowns or
options being shown in a random order).
The main issue is that in 99% of the case, it will be an oversight by the
dev, and cause the issue at hand. Do you see a valid use case using sets?
I do agree with the reporter that if we support sets(), we should also fix
the migration issue.
--
Ticket URL: <https://code.djangoproject.com/ticket/35854#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/01070192b3050845-0af5105c-fcf3-4535-83b4-4e3d09158ebc-000000%40eu-central-1.amazonses.com.
