#34964: Reversing the order of Q objects in a CheckConstraint generates a
migration
-------------------------------------+-------------------------------------
Reporter: Jacob Walls | Owner: Jacob
Type: | Walls
Cleanup/optimization | Status: assigned
Component: Migrations | Version: dev
Severity: Normal | Resolution:
Keywords: noop | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Mariusz Felisiak):
I have a gut feeling that it's not worth doing, as there is a risk of
potential regressions. If you modify `check` of `condition` you should be
ready to deal with consequences of recreating the index, even if they
theoretically have the same meaning 🤷 I'm not strongly against this
patch, this is just a friendly warning ;)
> ... with a table rebuild. That's something you might miss.
I know how migrations work on SQLite ;)
--
Ticket URL: <https://code.djangoproject.com/ticket/34964#comment:10>
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/0107018bccc31af1-7b9bf239-db89-4061-af5d-f5477a3d2d31-000000%40eu-central-1.amazonses.com.
