summaryrefslogtreecommitdiff
path: root/docs/ref/databases.txt
diff options
context:
space:
mode:
authorRan Benita <ran234@gmail.com>2017-04-11 18:52:53 +0300
committerTim Graham <timograham@gmail.com>2017-04-11 11:52:53 -0400
commit2a6b4e65214ff60ee50b14fb33916a2b58e9fcbe (patch)
tree1e44bf27bee8c10280a16b35cda3dbaaf6a6368f /docs/ref/databases.txt
parent5dbf1c4b23cda915369f4895be293369575238d0 (diff)
Updated docs after changing select_for_update() to raise NotSupportedError.
Follow up to 054a44d6f0f75395bd02a21e31ea904a24750a2b.
Diffstat (limited to 'docs/ref/databases.txt')
-rw-r--r--docs/ref/databases.txt3
1 files changed, 2 insertions, 1 deletions
diff --git a/docs/ref/databases.txt b/docs/ref/databases.txt
index 42e335c9c6..7960688202 100644
--- a/docs/ref/databases.txt
+++ b/docs/ref/databases.txt
@@ -569,7 +569,8 @@ Row locking with ``QuerySet.select_for_update()``
MySQL does not support the ``NOWAIT`` and ``SKIP LOCKED`` options to the
``SELECT ... FOR UPDATE`` statement. If ``select_for_update()`` is used with
-``nowait=True`` or ``skip_locked=True`` then a ``DatabaseError`` will be raised.
+``nowait=True`` or ``skip_locked=True``, then a
+:exc:`~django.db.NotSupportedError` is raised.
Automatic typecasting can cause unexpected results
--------------------------------------------------