#36852: postgres.contrib.ExclusionContraint __eq__ incorrectly considers
index_type
case
-------------------------------------+-------------------------------------
Reporter: haki | Owner: haki
Type: Bug | Status: assigned
Component: contrib.postgres | Version: dev
Severity: Normal | Resolution:
Keywords: | Triage Stage: Ready for
| checkin
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Jacob Walls):
I confirmed that changing an `index_type` from `spgist` to `SPGIST` no
longer creates a migration after this proposed change. Changes between
`gist` and `GIST` were already a no-op given how `deconstruct()` handles
the default value:
{{{#!py
def deconstruct(self):
...
if self.index_type.lower() != "gist":
kwargs["index_type"] = self.index_type
}}}
--
Ticket URL: <https://code.djangoproject.com/ticket/36852#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 visit
https://groups.google.com/d/msgid/django-updates/0107019b9e54007f-1b0ff6d3-ff76-4c72-8a23-8d9dc2cbe9a3-000000%40eu-central-1.amazonses.com.
