Changes between Version 24 and Version 25 of MultipleDatabaseSupport


Ignore:
Timestamp:
10/05/08 02:35:02 (6 years ago)
Author:
programmerq
Comment:

not a traclink

Legend:

Unmodified
Added
Removed
Modified
  • MultipleDatabaseSupport

    v24 v25  
    1919 * '''Connection selection''' - what is the API for telling Django which database a query should be executed against?
    2020 * '''Associating connections with models''' - for the common case where a model is assigned to a different database, how is that assignment made? How can existing apps such as contrib.auth be assigned to a different database in a clean way? This is one facet of the connection selection problem.
    21  * '''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?
     21 * '''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?
    2222 * '''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?
    2323 * '''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.
Back to Top