#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 Karl):
Replying to [comment:6 Natalia Bidart]:
> I disagree with this one. If a Django user uses a set(), I think they
may be up to two goals:
>
> 1. Either they made a mistake, and the infinite migrations make them
notice (and fix that), or
> 2. They intentionally did this and solve the migration issue by using a
callable.
Here's where I think that's a mistake: I didn't notice it right away and
created several migrations (3?) before noticing. I had even patched my
prod environment with it. A simple "check" on the model (not explicitly
part of migrations) likely would have caught it. Instead, I broke my
migrations trying to "undo" it and lost some data.
Of course, this is in a one-man-shop environment with no review, so
perhaps it's not a real issue on the global scale.
A lot of that is on me, but I don't see a "check" as a large burden and it
can be ignored if the dev is so inclined.
--
Ticket URL: <https://code.djangoproject.com/ticket/35854#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/01070192b620800c-96a94938-18e3-41fb-9149-ecf665075cc6-000000%40eu-central-1.amazonses.com.
