summaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorMariusz Felisiak <felisiak.mariusz@gmail.com>2024-03-18 16:11:38 +0100
committerGitHub <noreply@github.com>2024-03-18 16:11:38 +0100
commit9c17010358891c73417ec569df4f568c0671c099 (patch)
tree6e65087cb526809a1bade96d5ed3564d588e4f52 /docs
parent10b31eea337261ba724a71839ebc4bd4ddac3675 (diff)
Refs #34059, Refs #34060 -- Removed outdated warning about validation of JSONField constraints.
Known issues have been fixed in: - 0d8fbe2ade29f1b7bd9e6ba7a0281f5478603a43, - c991602ce5798385261381025c06698d7fd30dc5, and - 26aae5614487f58ddb1df5726224393887373ecd.
Diffstat (limited to 'docs')
-rw-r--r--docs/ref/models/constraints.txt11
-rw-r--r--docs/ref/models/instances.txt11
2 files changed, 0 insertions, 22 deletions
diff --git a/docs/ref/models/constraints.txt b/docs/ref/models/constraints.txt
index fd24eeee3a..6339c39679 100644
--- a/docs/ref/models/constraints.txt
+++ b/docs/ref/models/constraints.txt
@@ -34,17 +34,6 @@ option.
Constraints are checked during the :ref:`model validation
<validating-objects>`.
-.. admonition:: Validation of Constraints with ``JSONField``
-
- Constraints containing :class:`~django.db.models.JSONField` may not raise
- validation errors as key, index, and path transforms have many
- database-specific caveats. This :ticket:`may be fully supported later
- <34059>`.
-
- You should always check that there are no log messages, in the
- ``django.db.models`` logger, like *"Got a database error calling check() on
- …"* to confirm it's validated properly.
-
``BaseConstraint``
==================
diff --git a/docs/ref/models/instances.txt b/docs/ref/models/instances.txt
index 6d1a7e5db4..b203ff67c4 100644
--- a/docs/ref/models/instances.txt
+++ b/docs/ref/models/instances.txt
@@ -246,17 +246,6 @@ need to call a model's :meth:`~Model.full_clean()` method if you plan to handle
validation errors yourself, or if you have excluded fields from the
:class:`~django.forms.ModelForm` that require validation.
-.. warning::
-
- Constraints containing :class:`~django.db.models.JSONField` may not raise
- validation errors as key, index, and path transforms have many
- database-specific caveats. This :ticket:`may be fully supported later
- <34059>`.
-
- You should always check that there are no log messages, in the
- ``django.db.models`` logger, like *"Got a database error calling check() on
- …"* to confirm it's validated properly.
-
.. method:: Model.full_clean(exclude=None, validate_unique=True, validate_constraints=True)
This method calls :meth:`Model.clean_fields()`, :meth:`Model.clean()`,