[Django] #34760: Drop support for SQLite < 3.26.0

[Django]

#34760: Drop support for SQLite < 3.26.0
-------------------------------------+-------------------------------------
Reporter: Mariusz | Owner: nobody
Felisiak |
Type: | Status: new
Cleanup/optimization |
Component: Database | Version: 4.2
layer (models, ORM) |
Severity: Normal | Keywords:
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
SQLite 3.24+ supports updating rows on constraint or uniqueness errors
during `INSERT`.
SQLite 3.25+ supports window functions and renaming columns.
SQLite 3.26+ support DDL operations requiring references rename in a
transaction.

Ubuntu Focal ships with SQLite 3.31.1 (which will still by supported by
Django).
Debian Buster ships with 3.27.2 and will EOL in June 2024.
Python 3.8 ships with 3.28.0.

​SQLite 3.26.0 was released in December 2018. SQLite version support seems
like a similar situation as GEOS libraries which we generally support
about 5 years after released.

--
Ticket URL: <https://code.djangoproject.com/ticket/34760>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

[Django]

#34760: Drop support for SQLite < 3.26.0
-------------------------------------+-------------------------------------

Reporter: Mariusz Felisiak | Owner: Mariusz
Type: | Felisiak
Cleanup/optimization | Status: assigned
Component: Database layer | Version: 4.2
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0

Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Changes (by Mariusz Felisiak):

* owner: nobody => Mariusz Felisiak
* status: new => assigned

--
Ticket URL: <https://code.djangoproject.com/ticket/34760#comment:1>

[Django]

#34760: Drop support for SQLite < 3.26.0
-------------------------------------+-------------------------------------
Reporter: Mariusz Felisiak | Owner: Mariusz
Type: | Felisiak
Cleanup/optimization | Status: assigned
Component: Database layer | Version: 4.2
(models, ORM) |
Severity: Normal | Resolution:

Keywords: | Triage Stage: Accepted

Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Changes (by Natalia Bidart):

* stage: Unreviewed => Accepted

Comment:

Sounds good, though following the rationale I'm not sure I understand why
we wouldn't drop support for < 3.27?

--
Ticket URL: <https://code.djangoproject.com/ticket/34760#comment:2>

[Django]

#34760: Drop support for SQLite < 3.26.0
-------------------------------------+-------------------------------------
Reporter: Mariusz Felisiak | Owner: Mariusz
Type: | Felisiak
Cleanup/optimization | Status: assigned
Component: Database layer | Version: 4.2
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Comment (by Mariusz Felisiak):

Replying to [comment:2 Natalia Bidart]:

> Sounds good, though following the rationale I'm not sure I understand
why we wouldn't drop support for < 3.27?

3.27 will not be 5 years old, when Django 5.0 is released.

--
Ticket URL: <https://code.djangoproject.com/ticket/34760#comment:3>

[Django]

#34760: Drop support for SQLite < 3.26.0
-------------------------------------+-------------------------------------
Reporter: Mariusz Felisiak | Owner: Mariusz
Type: | Felisiak
Cleanup/optimization | Status: assigned
Component: Database layer | Version: 4.2
(models, ORM) |
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Comment (by Natalia Bidart):

Replying to [comment:3 Mariusz Felisiak]:

> Replying to [comment:2 Natalia Bidart]:
> > Sounds good, though following the rationale I'm not sure I understand
why we wouldn't drop support for < 3.27?
>
> 3.27 will not be 5 years old, when Django 5.0 is released.

Right, but 3.26 will be, so I was wondering if we should also drop 3.26.
From the ticket title I understood you mean drop every version less than
3.26? Or did you mean `<= 3.26`"?

--
Ticket URL: <https://code.djangoproject.com/ticket/34760#comment:4>