#33342: Allow ExclusionConstraint to use the OpClass expression
-------------------------------------+-------------------------------------
Reporter: Hannes Ljungberg | Owner: Hannes
| Ljungberg
Type: New feature | Status: assigned
Component: contrib.postgres | Version: dev
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Hannes Ljungberg):
> Sounds reasonable, maybe we should also deprecate the opclasses
argument.
Yup, that sounds like the proper way forward.
As a side note it would be interesting to look into the possibility of
deprecating the `fields` argument (and by that the `opclasses` argument)
on `Index` and `UniqueConstraint`. It would require us to make
`Index.contains_expressions` and `UniqueConstraint.contains_expressions` a
bit smarter.
--
Ticket URL: <https://code.djangoproject.com/ticket/33342#comment:3>
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/067.fd0efadba31cf9458064d6d1590971d2%40djangoproject.com.
