Opened 4 years ago

Closed 4 years ago

Last modified 4 years ago

#23144 closed Cleanup/optimization (fixed)

Drop support for MySQL 5.0, 5.1

Reported by: Tim Graham Owned by: Tim Graham
Component: Database layer (models, ORM) Version: master
Severity: Normal Keywords:
Cc: Triage Stage: Ready for checkin
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

The end of upstream support periods was reached in January 2012 for MySQL 5.0 and December 2013 for MySQL 5.1. As a consequence, Django 1.8 may set 5.5 as the minimum MySQL version it officially supports.

Change History (4)

comment:1 Changed 4 years ago by Tim Graham

Has patch: set

PR which is primarily updating links in the docs.

comment:2 Changed 4 years ago by merb

Triage Stage: AcceptedReady for checkin

comment:3 Changed 4 years ago by Tim Graham <timograham@…>

Resolution: fixed
Status: newclosed

In d28396f5268f1974ef1e84d13bcf1ac107005ced:

Fixed #23144 -- Dropped support for MySQL 5.0, 5.1.

comment:4 Changed 4 years ago by Tim Graham <timograham@…>

In 88b2a20f047347da86f448fe09a56251d29e4168:

Simplified MySQL storage engine detection using INFORMATION_SCHEMA.ENGINES table

Query the table introduced in MySQL 5.1; refs #23144.

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