mirrors/django
1
0
Fork 0
mirror of https://github.com/django/django.git synced 2025-08-04 02:48:35 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

Fixed #32908 -- Allowed select_for_update(skip_locked) on MariaDB 10.6+.

Browse source
This commit is contained in:
Mariusz Felisiak 2021-07-08 06:51:10 +02:00 • committed by GitHub
parent 5013798fe9
commit 77b88fe621
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
4 changed files with 16 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

14
docs/ref/models/querysets.txt
View file

@ -1792,11 +1792,11 @@ them::
>>> Person.objects.select_related('hometown').select_for_update().exclude(hometown=None)
<QuerySet [<Person: ...)>, ...]>
Currently, the ``postgresql``, ``oracle``, and ``mysql`` database
backends support ``select_for_update()``. However, MariaDB 10.3+ supports only
the ``nowait`` argument and MySQL 8.0.1+ supports the ``nowait``,
``skip_locked``, and ``of`` arguments. The ``no_key`` argument is supported
only on PostgreSQL.
The ``postgresql``, ``oracle``, and ``mysql`` database backends support
``select_for_update()``. However, MariaDB 10.3+ only supports the ``nowait``
argument, MariaDB 10.6+ also supports the ``skip_locked`` argument, and MySQL
8.0.1+ supports the ``nowait``, ``skip_locked``, and ``of`` arguments. The
``no_key`` argument is only supported on PostgreSQL.
Passing ``nowait=True``, ``skip_locked=True``, ``no_key=True``, or ``of`` to
``select_for_update()`` using database backends that do not support these
@ -1836,6 +1836,10 @@ raised if ``select_for_update()`` is used in autocommit mode.
The ``of`` argument was allowed on MySQL 8.0.1+.
.. versionchanged:: 4.0
The ``skip_locked`` argument was allowed on MariaDB 10.6+.
``raw()``
~~~~~~~~~