1
0
mirror of https://github.com/django/django.git synced 2025-07-20 09:39:13 +00:00

[1.9.x] Refs #25899 -- Improved visibility of TEST database settings in testing docs.

Backport of 738bda8a6feea95d07b73246365e75b3d25e3466 from master
This commit is contained in:
Tim Graham 2015-12-10 11:23:12 -05:00
parent 515f149e4d
commit 9f3ce6d987

View File

@ -153,14 +153,14 @@ when all the tests have been executed.
be created. Any migrations will also be applied in order to keep it be created. Any migrations will also be applied in order to keep it
up to date. up to date.
By default the test databases get their names by prepending ``test_`` The default test database names are created by prepending ``test_`` to the
to the value of the :setting:`NAME` settings for the databases value of each :setting:`NAME` in :setting:`DATABASES`. When using SQLite, the
defined in :setting:`DATABASES`. When using the SQLite database engine tests will use an in-memory database by default (i.e., the database will be
the tests will by default use an in-memory database (i.e., the created in memory, bypassing the filesystem entirely!). The :setting:`TEST
database will be created in memory, bypassing the filesystem <DATABASE-TEST>` dictionary in :setting:`DATABASES` offers a number of settings
entirely!). If you want to use a different database name, specify to configure your test database. For example, if you want to use a different
:setting:`NAME <TEST_NAME>` in the :setting:`TEST <DATABASE-TEST>` database name, specify :setting:`NAME <TEST_NAME>` in the :setting:`TEST
dictionary for any given database in :setting:`DATABASES`. <DATABASE-TEST>` dictionary for any given database in :setting:`DATABASES`.
On PostgreSQL, :setting:`USER` will also need read access to the built-in On PostgreSQL, :setting:`USER` will also need read access to the built-in
``postgres`` database. ``postgres`` database.