Author: mtredinnick
Date: 2007-05-07 21:33:10 -0500 (Mon, 07 May 2007)
New Revision: 5160
Modified:
django/trunk/docs/contributing.txt
Log:
Fixed #4226 -- Added DATABASE_NAME to the list of settings required to be
mentioned in the settings file for the tests to run. Thanks, Paul Smith.
Modified: django/trunk/docs/contributing.txt
===================================================================
--- django/trunk/docs/contributing.txt 2007-05-08 02:27:30 UTC (rev 5159)
+++ django/trunk/docs/contributing.txt 2007-05-08 02:33:10 UTC (rev 5160)
@@ -396,10 +396,11 @@
./runtests.py --settings=path.to.django.settings
Yes, the unit tests need a settings module, but only for database connection
-info -- the ``DATABASE_ENGINE``, ``DATABASE_USER`` and ``DATABASE_PASSWORD``.
-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.
+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.
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
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
