#36852: postgres.contrib.ExclusionContraint __eq__ incorrectly considers
index_type
case
-------------------------------------+-------------------------------------
Reporter: haki | Owner: haki
Type: Bug | Status: assigned
Component: Database | Version: dev
layer (models, ORM) |
Severity: Normal | Keywords:
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
The equality check for `ExclusionContraint` in
`postgres.contrib.ExclusionContraint` stores the index_type in the
provided case, but the equality check compares the string without
normalizing the case.
Unlike other props like condition where case might be important, the case
of `index_type` (currently 'gist', 'spgist', and soon 'hash') is not
significant, therefor should be ignored in equality checks.
--
Ticket URL: <https://code.djangoproject.com/ticket/36852>
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 visit
https://groups.google.com/d/msgid/django-updates/0107019b9ca282d9-1fac92c2-a3ca-46da-90a5-2c68ba0e36ea-000000%40eu-central-1.amazonses.com.
