mirror of
https://github.com/django/django.git
synced 2025-08-27 20:29:27 +00:00
[2.2.x] Removed unneeded non-breaking spaces added in 00169bc36
Backport of 8590726a5dd3087d40b549580703cd8c74f3d7b1 from master.
This commit is contained in:
parent
2525785880
commit
3b2701e4f2
@ -30,10 +30,10 @@ option.
|
|||||||
|
|
||||||
.. admonition:: Validation of Constraints
|
.. admonition:: Validation of Constraints
|
||||||
|
|
||||||
In general constraints are **not** checked during ``full_clean()``, and do
|
In general constraints are **not** checked during ``full_clean()``, and do
|
||||||
not raise ``ValidationError``\s. Rather you'll get a database integrity
|
not raise ``ValidationError``\s. Rather you'll get a database integrity
|
||||||
error on ``save()``. ``UniqueConstraint``\s are different in this regard,
|
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
|
enable two-stage validation. In addition to ``IntegrityError`` on
|
||||||
``save()``, ``ValidationError`` is also raised during model validation when
|
``save()``, ``ValidationError`` is also raised during model validation when
|
||||||
the ``UniqueConstraint`` is violated.
|
the ``UniqueConstraint`` is violated.
|
||||||
|
Loading…
x
Reference in New Issue
Block a user