Drop support for MySQL versions < 5.0.3

[Ramiro Morales]

The idea is to drop support of MySQL 4.x (and perhaps 5.0?) for Django 1.5. See:

• ​MySQL Product Support EOL Announcements
• ​Supported Platforms: MySQL Database
• ​MySQL Technical Support

The first document list the following relevant dates:

• January 9, 2012 -- Per Oracle's Lifetime Support policy, MySQL 5.0 is now covered under Oracle Sustaining Support.

• December 31, 2009 -- Per the MySQL Support Lifecycle policy, extended support for MySQL 4.1 ended on December 31, 2009. MySQL users are encouraged to upgrade to a current production release of MySQL. Customers needing upgrade assisitance should contact MySQL Support.

• December 31, 2009 -- Per the MySQL Support Lifecycle policy, active support for MySQL 5.0 ended on December 31, 2009. MySQL 5.0 is now in the Extended support phase.

[Claude Paroz]

Agreed (for 4.x at least).

[Ramiro Morales]

Regarding support of enterprise-grade Linux distributions, this is what I've found:

For RHEL, from:

• ​http://en.wikipedia.org/wiki/RHEL#Life_Cycle_Dates
• ​https://access.redhat.com/support/policy/updates/errata/
• ​http://distrowatch.com/table.php?distribution=redhat
• ​http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5/html/5.4_Technical_Notes/mysql.html

The currently vendor-supported OS version is 5.x that ships MySQL 5.0.y with y > 3.

Any information about versions of MySQL shipped with long-term support of other popular OS is welcome.

[Claude Paroz]

In Debian:

• oldstable (Lenny) is shipping 5.0.51, ​http://packages.debian.org/lenny/mysql-server-5.0
• stable (Squeeze) is shipping 5.1.61 ​http://packages.debian.org/squeeze/mysql-server-5.1

In Ubuntu:

• Ubuntu 8.04 LTS is shipping 5.0.95, ​http://packages.ubuntu.com/hardy/mysql-server-5.0
• Ubuntu Lucid 10.04 LTS is shipping 5.1.61, ​http://packages.ubuntu.com/lucid/mysql-server-5.1

[Ramiro Morales]

See also #14266.

I would like to propose 5.0.3 as the minimum supported MySQL version.

[Ramiro Morales]

The attached patch implements the proposed change. It doesn't actually enforce the minimum version with code, only with the docs. Postgres backend does the same.

[Claude Paroz]

Shouldn't the uses_savepoints be set to self._mysql_storage_engine() != 'MyISAM', unless we want to officially drop support for MyISAM?

In introspection.py, I think we can also drop the fallback code in get_key_columns, now that we can count on information_schema table presence.

[Ramiro Morales]

Replying to claudep:

Shouldn't the uses_savepoints be set to self._mysql_storage_engine() != 'MyISAM', unless we want to officially drop support for MyISAM?

Actuall, when the feature got added in r17341 (to fix #15507; ignore the MyIOSAM in the commit message should have read InnoDB) we implemented setting the value of uses_savepoints to depend only the MySQL version (5.0.3) and to be True even when the DB uses MyISAM to avoid having to perform the MySQL storage backend verification (MyISAM v. InnoDB) in normal usage. We perform such test only when running the Django test suite. I'm open to change this but we need to avoid problems like the one reported in #18135.

In introspection.py, I think we can also drop the fallback code in get_key_columns, now that we can count on information_schema table presence.

Thanks for finding this, will update the patch.

[Ramiro Morales]

Replying to ramiro:

Replying to claudep:

Shouldn't the uses_savepoints be set to self._mysql_storage_engine() != 'MyISAM', unless we want to officially drop support for MyISAM?

Actuall, when the feature got added in r17341 (to fix #15507; ignore the MyIOSAM in the commit message should have read InnoDB) we implemented setting the value of uses_savepoints to depend only the MySQL version (5.0.3) and to be True even when the DB uses MyISAM to avoid having to perform the MySQL storage backend verification (MyISAM v. InnoDB) in normal usage. We perform such test only when running the Django test suite. I'm open to change this but we need to avoid problems like the one reported in #18135.

I had forgot why I was reluctant to insert it in the normal non-testing code path. It is because the code that detects of the MySQL storage engine creates a table and examines a query sent afterwards.

I think we should simply set uses_savepoints when MySQL >= 5.0.3 and add a note to the savepoints+MySQL documentation su users using MyISAM shouldn't not rely in such Django+MySQL feature.

[Claude Paroz]

I think this is good to go, thanks.

[Ramiro Morales]

In [17921]:

Fixed #18116 -- Raised minimum MySQL version officially suported to 5.0.3.

Thanks Carl, Claude and Anssi for discussion and patch review.

[Ramiro Morales]

In [17923]:

Added documentation notes about lack of database savepoints support when using MySQL+MyISAM.

Refs #15507, #18116 and r17341, r17921.