#12541: Add support for describing master/slave arrangements in multi-db
------------------------------------------+---------------------------------
Reporter: russellm | Owner: nobody
Status: new | Milestone:
Component: Database layer (models, ORM) | Version: 1.2-alpha
Keywords: | Stage: Unreviewed
Has_patch: 0 |
------------------------------------------+---------------------------------
Django's multidb setup can be used to implement master/slave database
arrangements - however, there is no allowance made for the fact that an
object retrieved from a slave is actually compatible with an object
retrieved from the master (or, for that matter, another slave).
It should be possible to define data relationships in DATABASES, and have
instance._state.db reflect those relationships - i.e., the database state
should describe the actual data *source*, not just the databse from which
the data was retrieved.
Once this support is in place, the cross-database validation checks (that
were commented out just before the merge of the soc branch) can be
reintroduced. Those checks should be modified to check the source, not the
raw db alias.
There has been [http://groups.google.com/group/django-
developers/browse_thread/thread/286cc88ad9953df4 some initial discussion
on django-dev] about this subject.
--
Ticket URL: <http://code.djangoproject.com/ticket/12541>
Django <http://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en.
