Fixed #12118 -- Added shared cache support to SQLite in-memory testing.

2 files changed, 12 insertions, 0 deletions

diff --git a/docs/releases/1.8.txt b/docs/releases/1.8.txt
index 507aed6584..a34f3bf5b8 100644
--- a/docs/releases/1.8.txt
+++ b/docs/releases/1.8.txt
@@ -573,6 +573,10 @@ Tests
 
 * Added test client support for file uploads with file-like objects.
 
+* A shared cache is now used when testing with a SQLite in-memory database when
+  using Python 3.4+ and SQLite 3.7.13+. This allows sharing the database
+  between threads.
+
 Validators
 ^^^^^^^^^^
 
diff --git a/docs/topics/testing/overview.txt b/docs/topics/testing/overview.txt
index 913820adf5..bd4216e029 100644
--- a/docs/topics/testing/overview.txt
+++ b/docs/topics/testing/overview.txt
@@ -185,12 +185,20 @@ 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 a SQLite in-memory database with Python 3.4+ and SQLite 3.7.13+,
+`shared cache <https://www.sqlite.org/sharedcache.html>`_ will be enabled, so
+you can write tests with ability to share the database between threads.
+
 .. versionchanged:: 1.7
 
    The different options in the :setting:`TEST <DATABASE-TEST>` database
    setting used to be separate options in the database settings dictionary,
    prefixed with ``TEST_``.
 
+.. versionadded:: 1.8
+
+    The ability to use SQLite with a shared cache as described above was added.
+
 .. admonition:: Finding data from your production database when running tests?
 
     If your code attempts to access the database when its modules are compiled,