From 3b2701e4f22c7bda3c798fd434a3214d3538e535 Mon Sep 17 00:00:00 2001 From: Claude Paroz Date: Sat, 22 Jun 2019 10:26:14 +0200 Subject: [PATCH] [2.2.x] Removed unneeded non-breaking spaces added in 00169bc36 Backport of 8590726a5dd3087d40b549580703cd8c74f3d7b1 from master. --- docs/ref/models/constraints.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/ref/models/constraints.txt b/docs/ref/models/constraints.txt index aaadc78ee9..d172353326 100644 --- a/docs/ref/models/constraints.txt +++ b/docs/ref/models/constraints.txt @@ -30,10 +30,10 @@ option. .. admonition:: Validation of Constraints - In general constraints are **not** checked during ``full_clean()``, and do - not raise ``ValidationError``\s. Rather you'll get a database integrity + 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 + 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.