From 8a1768432b1ec3ecfa390ac5eb70dbfb0cff59b3 Mon Sep 17 00:00:00 2001 From: Tim Graham Date: Thu, 24 Aug 2017 14:56:09 -0400 Subject: Fixed #28552 -- Dropped support for MySQL 5.5. --- docs/ref/contrib/gis/db-api.txt | 10 +++++----- docs/ref/contrib/gis/functions.txt | 14 +++++++------- docs/ref/contrib/gis/install/index.txt | 2 +- docs/ref/databases.txt | 34 +++++++++------------------------- docs/releases/2.1.txt | 6 ++++++ 5 files changed, 28 insertions(+), 38 deletions(-) (limited to 'docs') diff --git a/docs/ref/contrib/gis/db-api.txt b/docs/ref/contrib/gis/db-api.txt index cce38a3711..453eaef966 100644 --- a/docs/ref/contrib/gis/db-api.txt +++ b/docs/ref/contrib/gis/db-api.txt @@ -379,12 +379,12 @@ Function PostGIS Oracle MySQL Spat :class:`Azimuth` X X (LWGEOM) :class:`BoundingCircle` X X :class:`Centroid` X X X X -:class:`Difference` X X X (≥ 5.6.1) X -:class:`Distance` X X X (≥ 5.6.1) X +:class:`Difference` X X X X +:class:`Distance` X X X X :class:`Envelope` X X X :class:`ForceRHR` X :class:`GeoHash` X X (≥ 5.7.5) X (LWGEOM) -:class:`Intersection` X X X (≥ 5.6.1) X +:class:`Intersection` X X X X :class:`IsValid` X X X (≥ 5.7.5) X (LWGEOM) :class:`Length` X X X X :class:`LineLocatePoint` X X @@ -397,10 +397,10 @@ Function PostGIS Oracle MySQL Spat :class:`Reverse` X X X :class:`Scale` X X :class:`SnapToGrid` X X -:class:`SymDifference` X X X (≥ 5.6.1) X +:class:`SymDifference` X X X X :class:`Transform` X X X :class:`Translate` X X -:class:`Union` X X X (≥ 5.6.1) X +:class:`Union` X X X X ==================================== ======= ============== =========== ========== Aggregate Functions diff --git a/docs/ref/contrib/gis/functions.txt b/docs/ref/contrib/gis/functions.txt index bde36d443d..66099c3317 100644 --- a/docs/ref/contrib/gis/functions.txt +++ b/docs/ref/contrib/gis/functions.txt @@ -208,7 +208,7 @@ value of the geometry. .. class:: Difference(expr1, expr2, **extra) -*Availability*: MySQL (≥ 5.6.1), `PostGIS +*Availability*: MySQL, `PostGIS `__, Oracle, SpatiaLite Accepts two geographic fields or expressions and returns the geometric @@ -220,8 +220,8 @@ geometry B. .. class:: Distance(expr1, expr2, spheroid=None, **extra) -*Availability*: MySQL (≥ 5.6.1), `PostGIS -`__, Oracle, SpatiaLite +*Availability*: MySQL, `PostGIS `__, +Oracle, SpatiaLite Accepts two geographic fields or expressions and returns the distance between them, as a :class:`~django.contrib.gis.measure.Distance` object. On MySQL, a raw @@ -307,7 +307,7 @@ __ https://en.wikipedia.org/wiki/Geohash .. class:: Intersection(expr1, expr2, **extra) -*Availability*: MySQL (≥ 5.6.1), `PostGIS +*Availability*: MySQL, `PostGIS `__, Oracle, SpatiaLite Accepts two geographic fields or expressions and returns the geometric @@ -480,7 +480,7 @@ Number of Arguments Description .. class:: SymDifference(expr1, expr2, **extra) -*Availability*: MySQL (≥ 5.6.1), `PostGIS +*Availability*: MySQL, `PostGIS `__, Oracle, SpatiaLite Accepts two geographic fields or expressions and returns the geometric @@ -522,8 +522,8 @@ parameters. .. class:: Union(expr1, expr2, **extra) -*Availability*: MySQL (≥ 5.6.1), `PostGIS -`__, Oracle, SpatiaLite +*Availability*: MySQL, `PostGIS `__, +Oracle, SpatiaLite Accepts two geographic fields or expressions and returns the union of both geometries. diff --git a/docs/ref/contrib/gis/install/index.txt b/docs/ref/contrib/gis/install/index.txt index acfbaa68a4..c547c9b268 100644 --- a/docs/ref/contrib/gis/install/index.txt +++ b/docs/ref/contrib/gis/install/index.txt @@ -59,7 +59,7 @@ supported versions, and any notes for each of the supported database backends: Database Library Requirements Supported Versions Notes ================== ============================== ================== ========================================= PostgreSQL GEOS, GDAL, PROJ.4, PostGIS 9.3+ Requires PostGIS. -MySQL GEOS, GDAL 5.5+ Not OGC-compliant; :ref:`limited functionality `. +MySQL GEOS, GDAL 5.6+ Not OGC-compliant; :ref:`limited functionality `. Oracle GEOS, GDAL 12.1+ XE not supported. SQLite GEOS, GDAL, PROJ.4, SpatiaLite 3.6.+ Requires SpatiaLite 4.0+ ================== ============================== ================== ========================================= diff --git a/docs/ref/databases.txt b/docs/ref/databases.txt index 821d6e8d1b..e7d474a81d 100644 --- a/docs/ref/databases.txt +++ b/docs/ref/databases.txt @@ -276,7 +276,7 @@ MySQL notes Version support --------------- -Django supports MySQL 5.5 and higher. +Django supports MySQL 5.6 and higher. Django's ``inspectdb`` feature uses the ``information_schema`` database, which contains detailed data on all database schemas. @@ -294,36 +294,20 @@ Storage engines MySQL has several `storage engines`_. You can change the default storage engine in the server configuration. -Until MySQL 5.5.4, the default engine was MyISAM_ [#]_. The main drawbacks of -MyISAM are that it doesn't support transactions or enforce foreign-key -constraints. On the plus side, it was the only engine that supported full-text -indexing and searching until MySQL 5.6.4. +MySQL's default storage engine is InnoDB_. This engine is fully transactional +and supports foreign key references. It's the recommended choice. However, the +InnoDB autoincrement counter is lost on a MySQL restart because it does not +remember the ``AUTO_INCREMENT`` value, instead recreating it as "max(id)+1". +This may result in an inadvertent reuse of :class:`~django.db.models.AutoField` +values. -Since MySQL 5.5.5, the default storage engine is InnoDB_. This engine is fully -transactional and supports foreign key references. It's probably the best -choice at this point. However, note that the InnoDB autoincrement counter -is lost on a MySQL restart because it does not remember the -``AUTO_INCREMENT`` value, instead recreating it as "max(id)+1". This may -result in an inadvertent reuse of :class:`~django.db.models.AutoField` values. - -If you upgrade an existing project to MySQL 5.5.5 and subsequently add some -tables, ensure that your tables are using the same storage engine (i.e. MyISAM -vs. InnoDB). Specifically, if tables that have a ``ForeignKey`` between them -use different storage engines, you may see an error like the following when -running ``migrate``:: - - _mysql_exceptions.OperationalError: ( - 1005, "Can't create table '\\db_name\\.#sql-4a8_ab' (errno: 150)" - ) +The main drawbacks of MyISAM_ are that it doesn't support transactions or +enforce foreign-key constraints. .. _storage engines: https://dev.mysql.com/doc/refman/en/storage-engines.html .. _MyISAM: https://dev.mysql.com/doc/refman/en/myisam-storage-engine.html .. _InnoDB: https://dev.mysql.com/doc/refman/en/innodb-storage-engine.html -.. [#] Unless this was changed by the packager of your MySQL package. We've - had reports that the Windows Community Server installer sets up InnoDB as - the default storage engine, for example. - .. _mysql-db-api-drivers: MySQL DB API Drivers diff --git a/docs/releases/2.1.txt b/docs/releases/2.1.txt index 55dfb09ea9..ead4d2fde3 100644 --- a/docs/releases/2.1.txt +++ b/docs/releases/2.1.txt @@ -200,6 +200,12 @@ Database backend API * ... +Dropped support for MySQL 5.5 +----------------------------- + +The end of upstream support for MySQL 5.5 is December 2018. Django 2.1 supports +MySQL 5.6 and higher. + Miscellaneous ------------- -- cgit v1.3