#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
-------------------------------------+-------------------------------------
Changes (by Simon Charette):
* stage: Unreviewed => Accepted
Comment:
The only thing that slightly worries me is that I've seen Postgres be very
finicky about the order of components in complex constraint when dealing
with conditional of functional indices and in these rare cases the order
matters even they are representing the same condition.
--
Ticket URL: <https://code.djangoproject.com/ticket/34964#comment:2>
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/0107018bbf10d29e-fa9b45fa-4dd3-40ea-bce3-84fc4e69a5c9-000000%40eu-central-1.amazonses.com.
