diff options
Diffstat (limited to 'docs/topics/forms/modelforms.txt')
| -rw-r--r-- | docs/topics/forms/modelforms.txt | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/docs/topics/forms/modelforms.txt b/docs/topics/forms/modelforms.txt index b320d7fc04..c02d4d7809 100644 --- a/docs/topics/forms/modelforms.txt +++ b/docs/topics/forms/modelforms.txt @@ -237,17 +237,17 @@ There are two main steps involved in validating a ``ModelForm``: 2. :ref:`Validating the model instance <validating-objects>` Just like normal form validation, model form validation is triggered implicitly -when calling :meth:`~django.forms.Form.is_valid()` or accessing the +when calling :meth:`~django.forms.Form.is_valid` or accessing the :attr:`~django.forms.Form.errors` attribute and explicitly when calling ``full_clean()``, although you will typically not use the latter method in practice. ``Model`` validation is triggered from within the form validation step right after the form's ``clean()`` method is called. First, the model's -:meth:`~django.db.models.Model.full_clean()` is called with +:meth:`~django.db.models.Model.full_clean` is called with ``validate_unique=False`` and ``validate_constraints=False``, then the model's -:meth:`~django.db.models.Model.validate_unique()` and -:meth:`~django.db.models.Model.validate_constraints()` methods are called in +:meth:`~django.db.models.Model.validate_unique` and +:meth:`~django.db.models.Model.validate_constraints` methods are called in order. .. warning:: |