From bb011cf809359da3f717e35b5e70fec7897dd22f Mon Sep 17 00:00:00 2001 From: Kevin Christopher Henry Date: Wed, 21 Aug 2013 15:38:07 -0400 Subject: [PATCH] Documentation -- Corrected error about Model.full_clean() Although the ModelForm validation code was changed to call Model.full_clean(), the documentation still said otherwise. The offending phrase was removed. --- docs/ref/models/instances.txt | 11 +++-------- 1 file changed, 3 insertions(+), 8 deletions(-) diff --git a/docs/ref/models/instances.txt b/docs/ref/models/instances.txt index 015393a408..6295eb0407 100644 --- a/docs/ref/models/instances.txt +++ b/docs/ref/models/instances.txt @@ -104,14 +104,9 @@ aren't present on your form from being validated since any errors raised could not be corrected by the user. Note that ``full_clean()`` will *not* be called automatically when you call -your model's :meth:`~Model.save()` method, nor as a result of -:class:`~django.forms.ModelForm` validation. In the case of -:class:`~django.forms.ModelForm` validation, :meth:`Model.clean_fields()`, -:meth:`Model.clean()`, and :meth:`Model.validate_unique()` are all called -individually. - -You'll need to call ``full_clean`` manually when you want to run one-step model -validation for your own manually created models. For example:: +your model's :meth:`~Model.save()` method. You'll need to call it manually +when you want to run one-step model validation for your own manually created +models. For example:: from django.core.exceptions import ValidationError try: