Opened 5 years ago

Closed 3 years ago

#14266 closed Cleanup/optimization (fixed)

Audit database backend support claims, particularly for MySQL

Reported by: carljm Owned by: nobody
Component: Documentation Version: master
Severity: Normal Keywords:
Cc: Triage Stage: Accepted
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

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.

Change History (9)

comment:1 Changed 5 years ago by carljm

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset
  • Triage Stage changed from Unreviewed to Accepted

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

comment:2 Changed 5 years ago by carljm

  • milestone set to 1.3
  • Version changed from 1.2 to SVN

comment:3 Changed 5 years ago by ramiro

See also #14618.

comment:4 Changed 5 years ago by adamnelson

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.

comment:5 Changed 4 years ago by julien

  • Severity set to Normal
  • Type set to Cleanup/optimization

comment:6 Changed 4 years ago by jacob

  • milestone 1.3 deleted

Milestone 1.3 deleted

comment:11 Changed 3 years ago by aaugustin

  • UI/UX unset

Change UI/UX from NULL to False.

comment:12 Changed 3 years ago by aaugustin

  • Easy pickings unset

Change Easy pickings from NULL to False.

comment:13 Changed 3 years ago by ramiro

  • Resolution set to fixed
  • Status changed from new to closed

Fixed in [17921].

Note: See TracTickets for help on using tickets.
Back to Top