From 1dd9c9c1fb9317a52461db4faa399211aeebdb34 Mon Sep 17 00:00:00 2001 From: Timo Graham Date: Sun, 28 Nov 2010 18:49:37 +0000 Subject: [PATCH] [1.2.X] Fixed #14791 - Clarify additional note on save(). Thanks OldTroll. Backport of r14740 from trunk. git-svn-id: http://code.djangoproject.com/svn/django/branches/releases/1.2.X@14741 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/topics/forms/modelforms.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/topics/forms/modelforms.txt b/docs/topics/forms/modelforms.txt index 65bc0ea2ea..23ed9a79ae 100644 --- a/docs/topics/forms/modelforms.txt +++ b/docs/topics/forms/modelforms.txt @@ -241,7 +241,7 @@ supplied, ``save()`` will update that instance. If it's not supplied, >>> f.save() Note that ``save()`` will raise a ``ValueError`` if the data in the form -doesn't validate -- i.e., ``if form.errors``. +doesn't validate -- i.e., if form.errors evaluates to True. This ``save()`` method accepts an optional ``commit`` keyword argument, which accepts either ``True`` or ``False``. If you call ``save()`` with