On 4/8/07, Merric Mercer <[EMAIL PROTECTED]> wrote: > However, I can't figure out how Django handles it. I can't see anything > in the documentation or the settings that would allow writes to be > handled by a different host to the reads.
The idea with both load balancing and DB replication is that Django doesn't need to know about them -- if Django had to know how many load balancers were in front of it or how many databases were in the cluster behind it, configuration would become much more complex for no good reason. So, for example, with databases you generally have a pooling connection manager between Django and the DB cluster, and Django talks to that instead of having to figure out how many databases to talk to and when to talk to each one. This is how we've done it a couple times, albeit with PostgreSQL; we've used pgpool to maintain the pool of database connections, and had Django talk to it. -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
