Please forgive my ignorance. I am not the sharpest knife out of the web development drawer. I have a question about database replication as it relates to Django.
I used to work at a place that had a somewhat high availability/performance/whatever application where we had a MySQL db replicated across multiple machines. All of the writes were done to the master and all of the reads were spread out across mulitple slave systems.This worked out well because the number of reads far exceeed the number of writes. Some time ago there was a thread(http://groups.google.com/group/django-users/browse_thread/thread/d08f4975da831bb/42a458eba506cda9?q=database+replication&rnum=1#42a458eba506cda9) on the Django list that alluded to adding this type of capability to Django. Where you could have one db host setup to handle the writes and have Django read from a different host. At least that is how I read the thread. I did a search and could not find any other info out there on this. Is this still something that is on the table? Or am I was off base and is this something that is not even needed/wanted? Again I apologize if I sound ignorant. I don't know any better. --Ray --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
