Fixed #28584 -- Dropped support for SQLite < 3.7.15.

This commit is contained in:
Tim Graham 2017-10-03 10:42:18 -04:00 committed by GitHub
parent 51d230e00b
commit 27193aea00
7 changed files with 11 additions and 44 deletions

View file

@ -487,9 +487,9 @@ Savepoints
A savepoint is a marker within a transaction that enables you to roll back
part of a transaction, rather than the full transaction. Savepoints are
available with the SQLite (≥ 3.6.8), PostgreSQL, Oracle and MySQL (when using
the InnoDB storage engine) backends. Other backends provide the savepoint
functions, but they're empty operations -- they don't actually do anything.
available with the SQLite, PostgreSQL, Oracle, and MySQL (when using the InnoDB
storage engine) backends. Other backends provide the savepoint functions, but
they're empty operations -- they don't actually do anything.
Savepoints aren't especially useful if you are using autocommit, the default
behavior of Django. However, once you open a transaction with :func:`atomic`,
@ -582,8 +582,8 @@ Database-specific notes
Savepoints in SQLite
--------------------
While SQLite ≥ 3.6.8 supports savepoints, a flaw in the design of the
:mod:`sqlite3` module makes them hardly usable.
While SQLite supports savepoints, a flaw in the design of the :mod:`sqlite3`
module makes them hardly usable.
When autocommit is enabled, savepoints don't make sense. When it's disabled,
:mod:`sqlite3` commits implicitly before savepoint statements. (In fact, it

View file

@ -177,7 +177,7 @@ control the particular collation used by the test database. See the
:doc:`settings documentation </ref/settings>` for details of these
and other advanced settings.
If using an SQLite in-memory database with SQLite 3.7.13+, `shared cache
If using an SQLite in-memory database with SQLite, `shared cache
<https://www.sqlite.org/sharedcache.html>`_ is enabled, so you can write tests
with ability to share the database between threads.