Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
Browse files

[1.7.x] Fixed #22417 -- Added additional documentation for refs #16969.

Thanks Jon Foster for the report.

Backport of 1b3a3fc from master
  • Loading branch information...
commit 0086c9eb48101b6dabefa7f9195ac7d197780f09 1 parent bc5d568
@timgraham timgraham authored
Showing with 9 additions and 0 deletions.
  1. +4 −0 docs/releases/1.7.txt
  2. +5 −0 docs/topics/testing/overview.txt
View
4 docs/releases/1.7.txt
@@ -1247,6 +1247,10 @@ Miscellaneous
The :attr:`~django.core.validators.RegexValidator.flags` attribute was added
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:
Features deprecated in 1.7
View
5 docs/topics/testing/overview.txt
@@ -173,6 +173,11 @@ entirely!). If you want to use a different database name, specify
:setting:`NAME <TEST_NAME>` in the :setting:`TEST <DATABASE-TEST>`
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
use all of the same database settings you have in your settings file:
:setting:`ENGINE <DATABASE-ENGINE>`, :setting:`USER`, :setting:`HOST`, etc. The
Please sign in to comment.
Something went wrong with that request. Please try again.