diff options
| author | Mariusz Felisiak <felisiak.mariusz@gmail.com> | 2023-01-12 13:20:08 +0100 |
|---|---|---|
| committer | Mariusz Felisiak <felisiak.mariusz@gmail.com> | 2023-01-17 11:49:15 +0100 |
| commit | 23ec318988cb22bef176b9d81e4091715a4f41ff (patch) | |
| tree | 6663ee059eb179ef78c13c6ed545ec36014dc253 /docs | |
| parent | 5c10041f4636c3dfe637924ab24da85dd657d790 (diff) | |
Refs #33342 -- Removed ExclusionConstraint.opclasses per deprecation timeline.
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/ref/contrib/postgres/constraints.txt | 28 | ||||
| -rw-r--r-- | docs/releases/3.2.txt | 4 | ||||
| -rw-r--r-- | docs/releases/5.0.txt | 3 |
3 files changed, 6 insertions, 29 deletions
diff --git a/docs/ref/contrib/postgres/constraints.txt b/docs/ref/contrib/postgres/constraints.txt index 5c50ddd3a5..fcf50b8b5f 100644 --- a/docs/ref/contrib/postgres/constraints.txt +++ b/docs/ref/contrib/postgres/constraints.txt @@ -12,7 +12,7 @@ PostgreSQL supports additional data integrity constraints available from the ``ExclusionConstraint`` ======================= -.. class:: ExclusionConstraint(*, name, expressions, index_type=None, condition=None, deferrable=None, include=None, opclasses=(), violation_error_message=None) +.. class:: ExclusionConstraint(*, name, expressions, index_type=None, condition=None, deferrable=None, include=None, violation_error_message=None) Creates an exclusion constraint in the database. Internally, PostgreSQL implements exclusion constraints using indexes. The default index type is @@ -133,32 +133,6 @@ used for queries that select only included fields ``include`` is supported for GiST indexes. PostgreSQL 14+ also supports ``include`` for SP-GiST indexes. -``opclasses`` -------------- - -.. attribute:: ExclusionConstraint.opclasses - -The names of the `PostgreSQL operator classes -<https://www.postgresql.org/docs/current/indexes-opclass.html>`_ to use for -this constraint. If you require a custom operator class, you must provide one -for each expression in the constraint. - -For example:: - - ExclusionConstraint( - name='exclude_overlapping_opclasses', - expressions=[('circle', RangeOperators.OVERLAPS)], - opclasses=['circle_ops'], - ) - -creates an exclusion constraint on ``circle`` using ``circle_ops``. - -.. deprecated:: 4.1 - - The ``opclasses`` parameter is deprecated in favor of using - :class:`OpClass() <django.contrib.postgres.indexes.OpClass>` in - :attr:`~ExclusionConstraint.expressions`. - ``violation_error_message`` --------------------------- diff --git a/docs/releases/3.2.txt b/docs/releases/3.2.txt index 0195e3cf6e..5668c1a6ad 100644 --- a/docs/releases/3.2.txt +++ b/docs/releases/3.2.txt @@ -247,8 +247,8 @@ Minor features * The new :attr:`.ExclusionConstraint.include` attribute allows creating covering exclusion constraints on PostgreSQL 12+. -* The new :attr:`.ExclusionConstraint.opclasses` attribute allows setting - PostgreSQL operator classes. +* The new ``ExclusionConstraint.opclasses`` attribute allows setting PostgreSQL + operator classes. * The new :attr:`.JSONBAgg.ordering` attribute determines the ordering of the aggregated elements. diff --git a/docs/releases/5.0.txt b/docs/releases/5.0.txt index c09973578a..3b1db9a9ad 100644 --- a/docs/releases/5.0.txt +++ b/docs/releases/5.0.txt @@ -311,3 +311,6 @@ to remove usage of these features. * The ``name`` argument of ``django.utils.functional.cached_property()`` is removed. + +* The ``opclasses`` argument of + ``django.contrib.postgres.constraints.ExclusionConstraint`` is removed. |