From 119c6005a616db20585950e915d91b4f40615707 Mon Sep 17 00:00:00 2001
From: Russell Keith-Magee <russell@keith-magee.com>
Date: Thu, 12 Jul 2007 12:48:27 +0000
Subject: [PATCH] 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
---
 docs/contributing.txt | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/contributing.txt b/docs/contributing.txt
index e58b06881a..0e8dff68f4 100644
--- a/docs/contributing.txt
+++ b/docs/contributing.txt
@@ -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),
 ``DATABASE_ENGINE``, ``DATABASE_USER`` and ``DATABASE_PASSWORD`` settings. You
 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
-for all the tests to pass.
+to be present) and a ``SITE_ID`` setting (any non-zero integer value will do)
+in order for all the tests to pass.
 
 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