From b719688b21febd9a04c8623126558cd06cc27b80 Mon Sep 17 00:00:00 2001 From: Mariusz Felisiak Date: Thu, 3 Aug 2023 18:54:29 +0200 Subject: Fixed #34761 -- Dropped support for MySQL < 8.0.11. --- docs/ref/databases.txt | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) (limited to 'docs/ref/databases.txt') diff --git a/docs/ref/databases.txt b/docs/ref/databases.txt index 0d0409180c..aa55446607 100644 --- a/docs/ref/databases.txt +++ b/docs/ref/databases.txt @@ -412,7 +412,7 @@ MySQL notes Version support --------------- -Django supports MySQL 8 and higher. +Django supports MySQL 8.0.11 and higher. Django's ``inspectdb`` feature uses the ``information_schema`` database, which contains detailed data on all database schemas. @@ -755,14 +755,14 @@ MySQL and MariaDB do not support some options to the ``SELECT ... FOR UPDATE`` statement. If ``select_for_update()`` is used with an unsupported option, then a :exc:`~django.db.NotSupportedError` is raised. -=============== ========= ========== +=============== ========= ===== Option MariaDB MySQL -=============== ========= ========== -``SKIP LOCKED`` X (≥10.6) X (≥8.0.1) -``NOWAIT`` X X (≥8.0.1) -``OF`` X (≥8.0.1) +=============== ========= ===== +``SKIP LOCKED`` X (≥10.6) X +``NOWAIT`` X X +``OF`` X ``NO KEY`` -=============== ========= ========== +=============== ========= ===== When using ``select_for_update()`` on MySQL, make sure you filter a queryset against at least a set of fields contained in unique constraints or only -- cgit v1.3