Author: russellm Date: 2010-01-27 21:04:24 -0600 (Wed, 27 Jan 2010) New Revision: 12335
Modified: django/trunk/docs/topics/db/multi-db.txt Log: Fixed #12715 -- Clarified the docs on the usage of database routers, especially regarding the default routing scheme. Thanks to Chris Curvey for the suggestion. Modified: django/trunk/docs/topics/db/multi-db.txt =================================================================== --- django/trunk/docs/topics/db/multi-db.txt 2010-01-28 02:17:30 UTC (rev 12334) +++ django/trunk/docs/topics/db/multi-db.txt 2010-01-28 03:04:24 UTC (rev 12335) @@ -92,10 +92,15 @@ 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 ---------------- -- 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.
