Docs update for mysql and postgresl: Mentioned test/db_test_base.py because

  that is the place where the default database parameters comes from.

git-svn-id: http://svn.roundup-tracker.org/svnroot/roundup/roundup/trunk@4625 57a73879-2fb5-44c3-a270-3262357dd7e2

diff --git a/doc/mysql.txt b/doc/mysql.txt
index c59e70c0f2170a0b5a70bd65e1e52b8fb702eab8..393a011618cf1c205080cfacb82dbf53578db077 100644 (file)
--- a/doc/mysql.txt
+++ b/doc/mysql.txt
@@ -37,8 +37,8 @@ this:
        FLUSH PRIVILEGES;
 
 2. If your administrator has provided you with database connection info, 
-   you can modify MYSQL_* constants in the file test/test_db.py with 
-   the correct values.
+   see the config values in 'test/db_test_base.py' 
+   about which database connection, name and user will be used.
 
 The MySQL database should not contain any tables. Tests will not 
 drop the database with existing data.

diff --git a/doc/postgresql.txt b/doc/postgresql.txt
index fd19a7ae5e5acb3af57ddf88ebd6359cea71265d..8fd6abc5626014866a7b5f58664229ce5043b763 100644 (file)
--- a/doc/postgresql.txt
+++ b/doc/postgresql.txt
@@ -25,10 +25,8 @@ Running the PostgreSQL unit tests
 
 The user that you're running the tests as will need to be able to access
 the postgresql database on the local machine and create and drop
-databases. Edit the ``test/test_postgresql.py`` database connection info if
-you wish to test against a different database.
-
-The test database will be called "rounduptest".
+databases. See the config values in 'test/db_test_base.py' 
+about which database connection, name and user will be used.
 
 
 Credit