Changes between Version 21 and Version 22 of MultipleDatabaseSupport

Timestamp:

Sep 12, 2008, 2:13:31 PM (16 years ago)

Author:

simon

Comment:

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

MultipleDatabaseSupport

@@ -11 +11 @@
  * '''Talking to existing or legacy databases''' while still allowing newer functionality to be developed on a different database dedicated solely to Django.
  * '''Sharding''', where rows within a single model are spread across multiple databases for improved write performance.
+ * '''Moving models between databases''' - e.g. for converting from MySQL to Postgres, or for shuffling items between shards.
 
 == Problems to solve ==
@@ -19 +20 @@
  * '''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?
  * '''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?
+ * '''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.
 
 == Implementations ==