From 6bc1b7d8cd4e15dd7557a94c1e8a05734ee8ef0d Mon Sep 17 00:00:00 2001 From: Alex Gaynor Date: Thu, 3 Dec 2009 20:57:53 +0000 Subject: [PATCH] [soc2009/multidb] Removed a documentation reference to Meta.using. Patch from Russell Keith-Magee. git-svn-id: http://code.djangoproject.com/svn/django/branches/soc2009/multidb@11793 bcc190cf-cafb-0310-a4f2-bffc1f526a37 --- docs/topics/db/multi-db.txt | 9 --------- 1 file changed, 9 deletions(-) diff --git a/docs/topics/db/multi-db.txt b/docs/topics/db/multi-db.txt index 5db692aee4..6d57372ae2 100644 --- a/docs/topics/db/multi-db.txt +++ b/docs/topics/db/multi-db.txt @@ -27,15 +27,6 @@ you choose. If at any time you attempt to access a database that isn't defined in your :setting:`DATABASES` setting then Django will raise a ``django.db.utils.ConnectionDoesNotExist`` exception. -Selecting a Database for a ``Model`` -==================================== - -In addition to the global default database for all models, it is possible to -select a default database on a per-model level. This is done using the -``using`` option in a model's inner ``Meta`` class. When provided this -database becomes the default database for all lookups, saves, and deletes for -this model. It can be overiden on a per-query basis as described below. - Selecting a Database for a ``QuerySet`` =======================================