Changes between Version 21 and Version 22 of MultipleDatabaseSupport


Ignore:
Timestamp:
09/12/08 14:13:31 (7 years ago)
Author:
simon
Comment:

Added note about moving models between databases and making models aware of where they were loaded from

Legend:

Unmodified
Added
Removed
Modified
  • MultipleDatabaseSupport

    v21 v22  
    1111 * '''Talking to existing or legacy databases''' while still allowing newer functionality to be developed on a different database dedicated solely to Django.
    1212 * '''Sharding''', where rows within a single model are spread across multiple databases for improved write performance.
     13 * '''Moving models between databases''' - e.g. for converting from MySQL to Postgres, or for shuffling items between shards.
    1314
    1415== Problems to solve ==
     
    1920 * '''Related managers''' - how do we deal with the case when the User model lives on one database but its related BlogEntrys live on a different database?
    2021 * '''Joins across different databases''' - do we try to get these working? If not, how do we detect them and what kind of error or warning do we present?
     22 * '''Should models be aware of which database they were loaded from?''' - if so, model.save() will be able to automatically remember the correct database connection. The ability to over-ride this (e.g. with `model.save(using='archive')`) would be useful for moving models between databases.
    2123
    2224== Implementations ==
Back to Top