#30055: Drop support for SQLite < 3.8.3
-------------------------------------+-------------------------------------
Reporter: Tim Graham | Owner: Tim
Type: | Graham
Cleanup/optimization | Status: closed
Component: Database layer | Version: master
(models, ORM) |
Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Comment (by Simon Charette):
It's really odd that it fails on manual constraint checking as
`connection.introspection.table_names` should only return existing table
names (thus `django_site` should exist).
Also
[https://github.com/django/django/blob/bff748df3e1e1c0077e02df2b77bda2b827ad129/django/db/backends/sqlite3/features.py#L42
constraint checking should not be performed in the first place during
tests on SQLite < 3.20]. I wonder if it has to do with something `pytest`
or `pytest-django` does.
--
Ticket URL: <https://code.djangoproject.com/ticket/30055#comment:6>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/067.edd04f2aef14ce79010deac559939d28%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
