This page describes an out-dated Django branch from 2006 which attempted to address #1142 by adding support for multiple database connections. The branch is here: source:/django/branches/multiple-db-support . This page is preserved purely for historic interest; you should not attempt to use the branch.

Status as of 3rd September 2006

FEATURE COMPLETE (alpha)

All features are implemented and all tests pass. Much work remains in documenting the new features and extending test coverage.

Most of the basic implementation is done, with the exception of the items in this todo list:

TODO	status
Fix django.core.management.syncdb. syncdb is not implemented correctly using new features.	DONE
Merge to trunk [3661]. This trunk changeset moves a number of test features and removes the othertests directory, and will need a lot of hand-merging	DONE in [3712]
OTHER_DATABASES not DATABASES	DONE
MODELS entry in OTHER_DATABASES not model._meta.db_connection	DONE
Move connection info to manager	DONE
Tests for thread/request isolation	DONE
Generate sql for dropping tables in django.db.backends.sql.ansi	DONE
Generate sql for resetting sequences in postgres backend SchemaBuilder subclass	DONE
When validating models, warn user if a model references another model that is configured to use a different connection	DONE
Create mutliple_db.txt doc documenting use of settings, transactions, etc.
Link to multiple db doc from other docs where appropriate
Review tests and extend where appropriate

The plan

• Avoid any change that impacts backward compatibility. The intent is to add new functionality for those who need it, not to change the most common use case of a single database connection.

• Add a new settings variable, OTHER_DATABASES. OTHER_DATABASES is a dict of named database connection parameter sets. In each set, the keys are the same as the standard database connection settings variables. Each set of settings may also define a list of models that will use that connection by default. Each item in the MODELS list may an app label (in which case it applies to all models with that app label) or app_label.Model, in which case it applies only to that specific model.

OTHER_DATABASES = { 
    'a': { 'DATABASE_ENGINE': 'sqlite3',
           'DATABASE_NAME': '/tmp/dba.db'
           'MODELS': ['app_label', 'app_label_2.Model']
    },
    'b': { 'DATABASE_ENGINE': 'sqlite3',
           'DATABASE_NAME': '/tmp/dbb.db'
    }}

• Add db attribute to Managers. This allows access to the connection that a model should use, as determined by settings. It may also be changed on the fly to use a different connection for a particular query or set of queries. When assigning to Manager.db, assign a django.db.ConnectionInfo; the easiest way to get one is from the django.db.connections dict.

class Artist(models.Model):
    name = models.CharField(maxlength=100)
    alive = models.BooleanField(default=True)

    def __str__(self):
        return self.name'
        
class Widget(models.Model):
    code = models.CharField(maxlength=10, unique=True)
    weight = models.IntegerField()

    def __str__(self):
        return self.code
  
settings.OTHER_DATABASES['a']['MODELS'] = ['Artist']
settings.OTHER_DATABASES['b']['MODELS'] = ['Widget']

# get the db connection
connection = Artist.objects.db.connection

# assign another connection
Widget.objects.db = connections['other_widget_connection']

• Allow transaction decorators, etc to take optional connections argument. Without that argument, transactions will apply across all connections already in use.

• Move generation of schema manipulating sql (CREATE TABLE, etc) from django.core.management into django.db.backends.ansi.sql. Schema statements are build with a SchemaBuilder instance; each backend gets an instance in its creation module as creation.builder.

• Add methods to Manager to support per-model installation. This will enable each model to be installed using the connection that it specifies. It causes some complications, mainly in determining the correct order in which to install. My current solution is to depend on the developer already having figure that out by defining her models in a sensible order; and, when that fails, punting any unresolved constraints to the end of the syncdb or install process. The manager methods will delegate to each model's backend to do the sql creation.