Browse files

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


git-svn-id: bcc190cf-cafb-0310-a4f2-bffc1f526a37
  • Loading branch information...
1 parent 8b34a01 commit 471a841147ca9bb6a5cae8981be6d66ec42966a0 @adrianholovaty adrianholovaty committed Jul 5, 2011
Showing with 4 additions and 0 deletions.
  1. +4 −0 docs/ref/models/querysets.txt
4 docs/ref/models/querysets.txt
@@ -1328,6 +1328,10 @@ memory. The former is more efficient. For example, instead of doing this::
+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

0 comments on commit 471a841

Please sign in to comment.