Master / Slave Database Replication Scenario

2009-08-16 Thread Haes
Hi, we are using master / slave database replication, no partitioning, just replicating the complete database to several slaves for performance reasons. This is making some problems with a newly developed Django project, which makes use of an existing database. Is there an (easy) way to use a di

Re: Master / Slave Database Replication Scenario

2009-08-16 Thread Matthias Kestenholz
On Sun, Aug 16, 2009 at 11:44 AM, Haes wrote: > > Hi, > > we are using master / slave database replication, no partitioning, > just replicating the complete database to several slaves for > performance reasons. This is making some problems with a newly > developed Django project, which makes use o

Re: Master / Slave Database Replication Scenario

2009-08-16 Thread Austin Gabel
Off the top of my head a couple of ideas come to mind. A quick and dirty way would be to have a separate Django project that only handles the admin app. Another way would be to make a custom model manager that would select the database to use. This way is a little more involved but not impossibl