From d94d7b113c21d7a0fd802fadb1adbbec8155e880 Mon Sep 17 00:00:00 2001 From: kola-er Date: Mon, 4 Nov 2019 22:44:10 +0100 Subject: Fixed #30928 -- Clarified MySQL/MariaDB support of QuerySet.select_for_update() options. Thanks Par Andersson for reporting the issue. --- docs/ref/models/querysets.txt | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) (limited to 'docs/ref/models') diff --git a/docs/ref/models/querysets.txt b/docs/ref/models/querysets.txt index e1d188b269..b8dcb90fec 100644 --- a/docs/ref/models/querysets.txt +++ b/docs/ref/models/querysets.txt @@ -1706,8 +1706,9 @@ them:: , ...]> Currently, the ``postgresql``, ``oracle``, and ``mysql`` database -backends support ``select_for_update()``. However, MySQL doesn't support the -``nowait``, ``skip_locked``, and ``of`` arguments. +backends support ``select_for_update()``. However, MariaDB 10.3+ supports only +the ``nowait`` argument and MySQL 8.0.1+ supports the ``nowait`` and +``skip_locked`` arguments. MySQL and MariaDB don't support the ``of`` argument. Passing ``nowait=True``, ``skip_locked=True``, or ``of`` to ``select_for_update()`` using database backends that do not support these -- cgit v1.3