mirror of
https://github.com/django/django.git
synced 2025-04-15 12:54:38 +00:00
[1.4.x] Fixed #14885 - Clarified that ModelForm cleaning may not fully complete if the form is invalid.
Thanks Ben Sturmfels for the patch. Backport of 3fd89d99036696ba08dd2dd7e20a5b375f85d23b from master.
This commit is contained in:
parent
b05d2f51b8
commit
42aee6ffe5
@ -200,10 +200,13 @@ The ``is_valid()`` method and ``errors``
|
||||
----------------------------------------
|
||||
|
||||
The first time you call ``is_valid()`` or access the ``errors`` attribute of a
|
||||
``ModelForm`` triggers form validation as well as :ref:`model validation
|
||||
<validating-objects>`. This has the side-effect of cleaning the model you pass
|
||||
to the ``ModelForm`` constructor. For instance, calling ``is_valid()`` on your
|
||||
form will convert any date fields on your model to actual date objects.
|
||||
``ModelForm`` triggers :ref:`form validation <form-and-field-validation>` as
|
||||
well as :ref:`model validation <validating-objects>`. This has the side-effect
|
||||
of cleaning the model you pass to the ``ModelForm`` constructor. For instance,
|
||||
calling ``is_valid()`` on your form will convert any date fields on your model
|
||||
to actual date objects. If form validation fails, only some of the updates
|
||||
may be applied. For this reason, you'll probably want to avoid reusing the
|
||||
model instance.
|
||||
|
||||
|
||||
The ``save()`` method
|
||||
|
Loading…
x
Reference in New Issue
Block a user