From dd2d76803c040a03342db1caa2b77747b4426549 Mon Sep 17 00:00:00 2001 From: jordanbae Date: Tue, 9 Jan 2024 23:04:31 +0900 Subject: [PATCH] [5.0.x] Fixed #34949 -- Clarified when UniqueConstraints with include/nulls_distinct are not created. Backport of 4fec1d2ce37241fb8fa001971c441d360ed2a196 from main --- docs/ref/models/constraints.txt | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/ref/models/constraints.txt b/docs/ref/models/constraints.txt index efe63a8ac1..cc308cedf2 100644 --- a/docs/ref/models/constraints.txt +++ b/docs/ref/models/constraints.txt @@ -229,7 +229,8 @@ For example:: will allow filtering on ``room`` and ``date``, also selecting ``full_name``, while fetching data only from the index. -``include`` is supported only on PostgreSQL. +Unique constraints with non-key columns are ignored for databases besides +PostgreSQL. Non-key columns have the same database restrictions as :attr:`Index.include`. @@ -272,7 +273,8 @@ For example:: creates a unique constraint that only allows one row to store a ``NULL`` value in the ``ordering`` column. -``nulls_distinct`` is ignored for databases besides PostgreSQL 15+. +Unique constraints with ``nulls_distinct`` are ignored for databases besides +PostgreSQL 15+. ``violation_error_code`` ------------------------