summaryrefslogtreecommitdiff
path: root/docs/ref
diff options
context:
space:
mode:
authorShai Berger <shai@platonix.com>2014-04-10 03:40:33 +0300
committerShai Berger <shai@platonix.com>2014-04-10 03:44:45 +0300
commitd5cef2a19c5a70766693264d08605f56d26e573d (patch)
tree13af5ce25fb1e4bcb70ee48954f9cc9d8f4eb9c0 /docs/ref
parent690a5984a3c0a706b8cc296bdcccd524b2079559 (diff)
[1.6.x] Documentation fixes for the select_for_update change.
Refs #22343; thanks Tim Graham for the fixes.
Diffstat (limited to 'docs/ref')
-rw-r--r--docs/ref/models/querysets.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/ref/models/querysets.txt b/docs/ref/models/querysets.txt
index 14e2cfac18..a7bbf4d290 100644
--- a/docs/ref/models/querysets.txt
+++ b/docs/ref/models/querysets.txt
@@ -1314,7 +1314,7 @@ do not support ``nowait``, such as MySQL, will cause a
:exc:`~django.db.DatabaseError` to be raised. This is in order to prevent code
unexpectedly blocking.
-Executing a queryset with ``select_for_update`` in autocommit mode is
+Evaluating a queryset with ``select_for_update`` in autocommit mode is
an error because the rows are then not locked. If allowed, this would
facilitate data corruption, and could easily be caused by calling,
outside of any transaction, code that expects to be run in one.