Added a note that full_validate will not be called automatically by model.save().
git-svn-id: http://code.djangoproject.com/svn/django/trunk@12103 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
parent
5b97a7b11b
commit
4d6c66d4d8
|
@ -44,6 +44,13 @@ message dict with errors from all fields.
|
||||||
|
|
||||||
To add your own validation logic, override the supplied ``validate()`` method:
|
To add your own validation logic, override the supplied ``validate()`` method:
|
||||||
|
|
||||||
|
Note that ``full_validate`` will NOT be called automatically when you call
|
||||||
|
your model's ``save()`` method. You will need to call it manually if you wish
|
||||||
|
to run your model validators. This is for the purposes of backwards
|
||||||
|
compatibility. However, if you are using a ``ModelForm``, it will call
|
||||||
|
``full_validate`` for you, and present any errors along with the other form
|
||||||
|
error messages.
|
||||||
|
|
||||||
.. method:: Model.validate()
|
.. method:: Model.validate()
|
||||||
|
|
||||||
The ``validate()`` method on ``Model`` by default checks for uniqueness of
|
The ``validate()`` method on ``Model`` by default checks for uniqueness of
|
||||||
|
|
Loading…
Reference in New Issue