Fixed #22417 -- Added additional documentation for refs #16969.

Thanks Jon Foster for the report.
This commit is contained in:
Tim Graham 2014-04-19 21:39:08 -04:00
parent 956bd64424
commit 1b3a3fc1e4
2 changed files with 9 additions and 0 deletions

View File

@ -1247,6 +1247,10 @@ Miscellaneous
The :attr:`~django.core.validators.RegexValidator.flags` attribute was added The :attr:`~django.core.validators.RegexValidator.flags` attribute was added
to :class:`~django.core.validators.RegexValidator` to simplify this change. to :class:`~django.core.validators.RegexValidator` to simplify this change.
* When running tests on PostgreSQL, the :setting:`USER` will need read access
to the built-in ``postgres`` database. This is in lieu of the previous
behavior of connecting to the actual non-test database.
.. _deprecated-features-1.7: .. _deprecated-features-1.7:
Features deprecated in 1.7 Features deprecated in 1.7

View File

@ -158,6 +158,11 @@ entirely!). If you want to use a different database name, specify
:setting:`NAME <TEST_NAME>` in the :setting:`TEST <DATABASE-TEST>` :setting:`NAME <TEST_NAME>` in the :setting:`TEST <DATABASE-TEST>`
dictionary for any given database in :setting:`DATABASES`. dictionary for any given database in :setting:`DATABASES`.
.. versionchanged:: 1.7
On PostgreSQL, :setting:`USER` will also need read access to the built-in
``postgres`` database.
Aside from using a separate database, the test runner will otherwise Aside from using a separate database, the test runner will otherwise
use all of the same database settings you have in your settings file: use all of the same database settings you have in your settings file:
:setting:`ENGINE <DATABASE-ENGINE>`, :setting:`USER`, :setting:`HOST`, etc. The :setting:`ENGINE <DATABASE-ENGINE>`, :setting:`USER`, :setting:`HOST`, etc. The