diff options
| author | Russell Keith-Magee <russell@keith-magee.com> | 2010-01-28 03:04:24 +0000 |
|---|---|---|
| committer | Russell Keith-Magee <russell@keith-magee.com> | 2010-01-28 03:04:24 +0000 |
| commit | 7856a759d0af09bf6295087941a4dfc5e6589d72 (patch) | |
| tree | 9b3fab6e2d597ae00ae6c7e788ba95d8b30782f9 /docs | |
| parent | 70aee5b48f3142175fa0fa016510c8484000252e (diff) | |
Fixed #12715 -- Clarified the docs on the usage of database routers, especially regarding the default routing scheme. Thanks to Chris Curvey for the suggestion.
git-svn-id: http://code.djangoproject.com/svn/django/trunk@12335 bcc190cf-cafb-0310-a4f2-bffc1f526a37
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/topics/db/multi-db.txt | 11 |
1 files changed, 8 insertions, 3 deletions
diff --git a/docs/topics/db/multi-db.txt b/docs/topics/db/multi-db.txt index 73872e6b53..2b2084a980 100644 --- a/docs/topics/db/multi-db.txt +++ b/docs/topics/db/multi-db.txt @@ -92,9 +92,14 @@ Automatic database routing The easiest way to use multiple databases is to set up a database routing scheme. The default routing scheme ensures that objects remain 'sticky' to their original database (i.e., an object retrieved from -the ``foo`` database will be saved on the same database). However, you -can implement more interesting behaviors by defining a different -routing scheme. +the ``foo`` database will be saved on the same database). The default +routing scheme ensures that if a database isn't specified, all queries +fall back to the ``default`` database. + +You don't have to do anything to activate the default routing scheme +-- it is provided 'out of the box' on every Django project. However, +if you want to implement more interesting database allocation +behaviors, you can define and install your own database routers. Database routers ---------------- |