diff options
| author | Mariusz Felisiak <felisiak.mariusz@gmail.com> | 2022-07-08 13:30:12 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2022-07-08 13:30:12 +0200 |
| commit | eb3699ea775548a22e0407ad12bf8cbdeaf95ff5 (patch) | |
| tree | bed4fed56dfc92b6808de048d1c2b6132d064ed4 /docs/ref/databases.txt | |
| parent | ccbf714ebeff51d1370789e5e487a978d0e2dbfb (diff) | |
Fixed #33718 -- Dropped support for MySQL 5.7.
Diffstat (limited to 'docs/ref/databases.txt')
| -rw-r--r-- | docs/ref/databases.txt | 11 |
1 files changed, 5 insertions, 6 deletions
diff --git a/docs/ref/databases.txt b/docs/ref/databases.txt index 05ae78b876..442b1a15a3 100644 --- a/docs/ref/databases.txt +++ b/docs/ref/databases.txt @@ -352,7 +352,7 @@ MySQL notes Version support --------------- -Django supports MySQL 5.7 and higher. +Django supports MySQL 8 and higher. Django's ``inspectdb`` feature uses the ``information_schema`` database, which contains detailed data on all database schemas. @@ -535,11 +535,10 @@ Several other `MySQLdb connection options`_ may be useful, such as ``ssl``, Setting ``sql_mode`` ~~~~~~~~~~~~~~~~~~~~ -From MySQL 5.7 onward, the default value of the ``sql_mode`` option contains -``STRICT_TRANS_TABLES``. That option escalates warnings into errors when data -are truncated upon insertion, so Django highly recommends activating a -`strict mode`_ for MySQL to prevent data loss (either ``STRICT_TRANS_TABLES`` -or ``STRICT_ALL_TABLES``). +The default value of the ``sql_mode`` option contains ``STRICT_TRANS_TABLES``. +That option escalates warnings into errors when data are truncated upon +insertion, so Django highly recommends activating a `strict mode`_ for MySQL to +prevent data loss (either ``STRICT_TRANS_TABLES`` or ``STRICT_ALL_TABLES``). .. _strict mode: https://dev.mysql.com/doc/refman/en/sql-mode.html#sql-mode-strict |