The django book's chapter on deployment mentions the use of Database replication as a means to scale using MySQL.
My understanding with Database replication is it uses a MASTER DB and a number of SLAVES. The master updates the slaves, asynchronously. This means that the slaves are used for reading data only and only the master is used for writing data. As the number of reads typically exceed the number of writes replication is supposed to work well. 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. Is there a way to do this? MerMer --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
