Added another bit to the update() queryset docs about avoiding race conditions

git-svn-id: http://code.djangoproject.com/svn/django/trunk@16517 bcc190cf-cafb-0310-a4f2-bffc1f526a37

1 files changed, 4 insertions, 0 deletions

diff --git a/docs/ref/models/querysets.txt b/docs/ref/models/querysets.txt
index 68a37ab6fd..aaf6a97a03 100644
--- a/docs/ref/models/querysets.txt
+++ b/docs/ref/models/querysets.txt
@@ -1328,6 +1328,10 @@ memory. The former is more efficient. For example, instead of doing this::
 
     Entry.objects.get(id=10).update(comments_on=False)
 
+Using ``update()`` instead of loading the object into memory also prevents a
+race condition where something might change in your database in the short
+period of time between loading the object and calling ``save()``.
+
 Finally, note that the ``update()`` method does an update at the SQL level and,
 thus, does not call any ``save()`` methods on your models, nor does it emit the
 ``pre_save`` or ``post_save`` signals (which are a consequence of calling