Django/django
11
0
Fork 0
Code Pull Requests Projects Releases Activity

[1.5.X] Fixed #19775 - Clarified requirements of the "default" database.

Browse Source 
Thanks monkut for the report and wsmith323 for the patch.

Backport of 31bcb102b2 from master
This commit is contained in:
Tim Graham 2013-02-23 15:21:35 -05:00
parent 29b0d89ee9
commit fceafa1929
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/topics/db/multi-db.txt
View File

@ -21,8 +21,10 @@ documentation.
Databases can have any alias you choose. However, the alias Databases can have any alias you choose. However, the alias
``default`` has special significance. Django uses the database with ``default`` has special significance. Django uses the database with
the alias of ``default`` when no other database has been selected. If the alias of ``default`` when no other database has been selected. If
you don't have a ``default`` database, you need to be careful to the concept of a ``default`` database doesn't make sense in the context
always specify the database that you want to use. of your project, you need to be careful to always specify the database
that you want to use. Django requires that a ``default`` database entry
be defined, but the parameters can be left blank if it will not be used.
The following is an example ``settings.py`` snippet defining two The following is an example ``settings.py`` snippet defining two
databases -- a default PostgreSQL database and a MySQL database called databases -- a default PostgreSQL database and a MySQL database called