From 0088e592922e2a711815cdb90a2610a1f1704a9a Mon Sep 17 00:00:00 2001 From: Mariusz Felisiak Date: Thu, 18 Jul 2019 12:56:25 +0200 Subject: [PATCH] [2.2.x] Refs #30547 -- Clarified that partial UniqueConstraints don't affect model validation. Backport of 230d75f59c43b9731465c4ec92ad714e301637b8 from master --- docs/ref/models/constraints.txt | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/docs/ref/models/constraints.txt b/docs/ref/models/constraints.txt index d172353326..1d75a9ede4 100644 --- a/docs/ref/models/constraints.txt +++ b/docs/ref/models/constraints.txt @@ -32,11 +32,12 @@ option. In general constraints are **not** checked during ``full_clean()``, and do not raise ``ValidationError``\s. Rather you'll get a database integrity - error on ``save()``. ``UniqueConstraint``\s are different in this regard, - in that they leverage the existing ``validate_unique()`` logic, and thus - enable two-stage validation. In addition to ``IntegrityError`` on - ``save()``, ``ValidationError`` is also raised during model validation when - the ``UniqueConstraint`` is violated. + error on ``save()``. ``UniqueConstraint``\s without a + :attr:`~UniqueConstraint.condition` (i.e. non-partial unique constraints) + are different in this regard, in that they leverage the existing + ``validate_unique()`` logic, and thus enable two-stage validation. In + addition to ``IntegrityError`` on ``save()``, ``ValidationError`` is also + raised during model validation when the ``UniqueConstraint`` is violated. ``CheckConstraint`` ===================