Audit database backend support claims, particularly for MySQL

[Carl Meyer]

The ​documentation currently claims that it "may be possible" to use MySQL versions as far back as 3.23. It would be good to clarify exactly which versions are supported for all built-in database backends. This includes reviewing what versions are in use by e.g. RedHat Enterprise Linux, to get an idea which versions would be good for Django to still support, and checking which versions are in fact currently usable.

This has been done relatively recently for PostgreSQL, so a quick sanity check may be all that's necessary there; it's MySQL that's particularly out of date.

[Carl Meyer]

Filed at the request of Malcolm and Russell at the sprints; marking Accepted accordingly.

[Ramiro Morales]

See also #14618.

[Adam Nelson]

I've looked through the django-users group and the RHEL 4 docs and I think you'll be hard pressed to find even one user who will be trying to upgrade to Django 1.3 with anything less than MySQL 4.1. I couldn't find any references to v4.0 or v3.23 in the last 3 years on the group.

In addition, I don't know of anybody who uses or tests on MySQL 4.0 or lower. I think we should just leave out 3.23 and 4.0 from the notes and if those versions continue to work, great.

Here are the release notes for ​version 5.1 and ​version 5.5 which should be distilled into two new sections under MySQL.

[Jacob]

Milestone 1.3 deleted

[Aymeric Augustin]

Change UI/UX from NULL to False.

[Aymeric Augustin]

Change Easy pickings from NULL to False.

[Ramiro Morales]

Fixed in [17921].