#33342: Allow ExclusionConstraint to use the OpClass expression
-------------------------------------+-------------------------------------
Reporter: Hannes | Owner: Hannes Ljungberg
Ljungberg |
Type: New | Status: assigned
feature |
Component: | Version: dev
contrib.postgres |
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 |
-------------------------------------+-------------------------------------
To bring `ExclusionConstraint` in line with `Index` and `UniqueConstraint`
I think we should allow usage of the
[https://docs.djangoproject.com/en/3.2/ref/contrib/postgres/indexes
/#opclass-expressions OpClass] expressions. To support this we would make
`ExclusionConstraint` use the DDL reference classes instead of a templated
SQL string plus usage of the `IndexExpression` class.
--
Ticket URL: <https://code.djangoproject.com/ticket/33342>
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 django-updates+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/052.d4ba1100a2484222d5cfce891c9dbbf1%40djangoproject.com.
