Changes between Version 2 and Version 3 of MultipleDatabaseSupport


Ignore:
Timestamp:
Jun 8, 2006, 2:14:12 PM (18 years ago)
Author:
jpellerin@…
Comment:

Add current status

Legend:

Unmodified
Added
Removed
Modified
  • MultipleDatabaseSupport

    v2 v3  
    5050
    5151 * 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.
     52
     53=== Current status ===
     54
     55Current patch is attached. It implements most of the model-level changes, a few manager-level changes, and table creation for postgres and sqlite. It does not implement any transaction changes, and nothing has been removed yet from django.core.management; the model table cration code there has just been adapted in django.db.backends.ansi.creation.
Back to Top