Fixed #36105 -- Dropped support for MariaDB 10.5.

This commit is contained in:
Mariusz Felisiak 2025-02-09 12:57:40 +01:00 committed by GitHub
parent 0bac41fc7e
commit 17160819f3
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
6 changed files with 18 additions and 49 deletions

View file

@ -417,7 +417,7 @@ non-durable <https://www.postgresql.org/docs/current/non-durability.html>`_.
MariaDB notes
=============
Django supports MariaDB 10.5 and higher.
Django supports MariaDB 10.6 and higher.
To use MariaDB, use the MySQL backend, which is shared between the two. See the
:ref:`MySQL notes <mysql-notes>` for more details.
@ -774,7 +774,7 @@ a :exc:`~django.db.NotSupportedError` is raised.
=============== ========= =====
Option MariaDB MySQL
=============== ========= =====
``SKIP LOCKED`` X (≥10.6) X
``SKIP LOCKED`` X X
``NOWAIT`` X X
``OF`` X
``NO KEY``

View file

@ -259,9 +259,8 @@ Exactly one of ``old_name`` and ``old_fields`` can be provided. ``old_fields``
is an iterable of the strings, often corresponding to fields of
``index_together`` (pre-Django 5.1 option).
On databases that don't support an index renaming statement (SQLite and MariaDB
< 10.5.2), the operation will drop and recreate the index, which can be
expensive.
On databases that don't support an index renaming statement (SQLite), the
operation will drop and recreate the index, which can be expensive.
``AddConstraint``
-----------------