mirror of
https://github.com/django/django.git
synced 2024-12-23 09:36:06 +00:00
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
This commit is contained in:
parent
70aee5b48f
commit
7856a759d0
@ -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
|
||||
----------------
|
||||
|
Loading…
Reference in New Issue
Block a user