Index: docs/ref/models/instances.txt =================================================================== --- docs/ref/models/instances.txt (revision 12833) +++ docs/ref/models/instances.txt (working copy) @@ -34,12 +34,18 @@ .. versionadded:: 1.2 -There are three steps in validating a model, and all three are called by a -model's ``full_clean()`` method. Most of the time, this method will be called -automatically by a ``ModelForm``. (See the :ref:`ModelForm documentation -` for more information.) You should only need to call -``full_clean()`` if you plan to handle validation errors yourself. +There are three steps in validating a model: + * Validate the model fields + * Validate the model as a whole + * Validate the field uniqueness + +All three steps are performed by a model's ``full_clean()`` method. +Most of the time, each step is performed automatically via the is_valid method of ``ModelForm``. (See the :ref:`ModelForm documentation ` +for more information.) +You should only need to call a model's ``full_clean()`` method if you plan to +handle validation errors yourself. + .. method:: Model.full_clean(exclude=None) This method calls ``Model.clean_fields()``, ``Model.clean()``, and @@ -52,9 +58,8 @@ 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 ``save()`` method. You'll need to call it manually if you want -to run model validation outside of a ``ModelForm``. (This is for backwards -compatibility.) +your model's ``save()`` method, nor through ``ModelForm`` validation. +You'll need to call it manually when you want to run model validation outside of a ``ModelForm``. (This is for backwards compatibility.) Example::