diff options
| author | Shai Berger <shai@platonix.com> | 2014-04-10 03:40:33 +0300 |
|---|---|---|
| committer | Shai Berger <shai@platonix.com> | 2014-04-10 03:43:05 +0300 |
| commit | 941f947bfd8d8f1a608634cf42f212b3a5a1933c (patch) | |
| tree | 07ad26aef6a3a113a412f054e08c8db7d6dc33da /docs/ref | |
| parent | 3a9a4570efc933a50efec27bdd06af11877eeac6 (diff) | |
[1.7.x] Documentation fixes for the select_for_update change.
Refs #22343; thanks Tim Graham for the fixes.
Backport of 59b1d30 from master
Diffstat (limited to 'docs/ref')
| -rw-r--r-- | docs/ref/models/querysets.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/ref/models/querysets.txt b/docs/ref/models/querysets.txt index dce93e7096..4de02bf0d9 100644 --- a/docs/ref/models/querysets.txt +++ b/docs/ref/models/querysets.txt @@ -1378,7 +1378,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. |
