summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
Diffstat (limited to 'docs')
-rw-r--r--docs/ref/models/constraints.txt10
1 files changed, 6 insertions, 4 deletions
diff --git a/docs/ref/models/constraints.txt b/docs/ref/models/constraints.txt
index c675903db6..dd49b1cafc 100644
--- a/docs/ref/models/constraints.txt
+++ b/docs/ref/models/constraints.txt
@@ -35,10 +35,12 @@ option.
not raise ``ValidationError``\s. Rather you'll get a database integrity
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.
+ and :attr:`~UniqueConstraint.expressions` (i.e. non-functional 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``
===================