innov
/
django1
1
0
Fork 0
Code Issues Pull Requests 1 Projects Releases Wiki Activity

Fixed #4745 -- Updated docs to point out that 0 is not a valid SITE_ID when running the tests. Thanks for the suggestion, Lars Stavholm <stava@telcotec.se>. 

git-svn-id: http://code.djangoproject.com/svn/django/trunk@5664 bcc190cf-cafb-0310-a4f2-bffc1f526a37
This commit is contained in:
Russell Keith-Magee 2007-07-12 12:48:27 +00:00
parent f3e71048c3
commit 119c6005a6
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/contributing.txt
View File

@ -532,8 +532,8 @@ Yes, the unit tests need a settings module, but only for database connection
info -- the ``DATABASE_NAME`` (required, but will be ignored), info -- the ``DATABASE_NAME`` (required, but will be ignored),
``DATABASE_ENGINE``, ``DATABASE_USER`` and ``DATABASE_PASSWORD`` settings. You ``DATABASE_ENGINE``, ``DATABASE_USER`` and ``DATABASE_PASSWORD`` settings. You
will also need a ``ROOT_URLCONF`` setting (its value is ignored; it just needs will also need a ``ROOT_URLCONF`` setting (its value is ignored; it just needs
to be present) and a ``SITE_ID`` setting (any integer value will do) in order to be present) and a ``SITE_ID`` setting (any non-zero integer value will do)
for all the tests to pass. in order for all the tests to pass.
The unit tests will not touch your existing databases; they create a new The unit tests will not touch your existing databases; they create a new
database, called ``django_test_db``, which is deleted when the tests are database, called ``django_test_db``, which is deleted when the tests are