diff options
| author | Tim Graham <timograham@gmail.com> | 2012-10-16 20:39:13 -0400 |
|---|---|---|
| committer | Tim Graham <timograham@gmail.com> | 2012-10-16 20:47:07 -0400 |
| commit | 6ebb6f918872c2a714ddb9808984e70daaa95cd8 (patch) | |
| tree | ee447d2534b8d933104d0603f941c60ecd1b5cbb | |
| parent | 81020708eae0a38b56cad86a043a78ffac9ba32a (diff) | |
[1.4.X] Fixed #18548 - Clarified note regarding reusing model instances when form validation fails.
Backport of fd02bcff4a from master
| -rw-r--r-- | docs/topics/forms/modelforms.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/topics/forms/modelforms.txt b/docs/topics/forms/modelforms.txt index a29da70742..091073fb0c 100644 --- a/docs/topics/forms/modelforms.txt +++ b/docs/topics/forms/modelforms.txt @@ -206,7 +206,7 @@ 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. +model instance passed to the form, especially if validation fails. The ``save()`` method |