#16255 closed Cleanup/optimization (fixed)
Drop support for Posgres versions < 8.2 for Django 1.4
Reported by: | Ramiro Morales | Owned by: | nobody |
---|---|---|---|
Component: | Database layer (models, ORM) | Version: | dev |
Severity: | Normal | Keywords: | |
Cc: | Triage Stage: | Accepted | |
Has patch: | yes | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
A year ago a discussion was started in the django-dev mailing list about making official the minimum PostgreSQL version to be supported by Django for the in-development 1.3 release.
No clear consensus was reached and so, no action items resulted from it.
This ticket proposes simply dropping support for anything older that 8.2. Both 8.0 and 8.1 reached EOL in Nov 2010. See http://wiki.postgresql.org/wiki/PostgreSQL_Release_Support_Policy
The resulting code cleaanup could help in fixing #10509, #11285, #12180
Attachments (2)
Change History (9)
comment:1 by , 13 years ago
Summary: | Drop support for Posgres versions < 8.0 for Django 8.4 → Drop support for Posgres versions < 8.0 for Django 1.4 |
---|
comment:2 by , 13 years ago
comment:3 by , 13 years ago
Has patch: | set |
---|
comment:4 by , 13 years ago
Summary: | Drop support for Posgres versions < 8.0 for Django 1.4 → Drop support for Posgres versions < 8.2 for Django 1.4 |
---|
comment:5 by , 13 years ago
Triage Stage: | Unreviewed → Accepted |
---|
This looks reasonable.
If people are unable to upgrade to PostgreSQL 8.2 or later, they will also be unable to upgrade to Django 1.4; we can live with that.
Replying to ramiro:
For completeness, this is wrong, there was one change to the databases notes document explicitly marking 8.0 as the minimum but suggesting going for 8.2: https://code.djangoproject.com/changeset/13363/django/trunk/docs/ref/databases.txt