On 10/2/07, Andrey Khavryuchenko <[EMAIL PROTECTED]> wrote: > Shouldn't it? In case of MySQL replication (which is quite widely used) > and transactions someone somehow *has* to decide where the whole > transaction is going - to a master or to a slave.
In the case of MySQL, use MySQL Cluster, which designates a "SQL Node" to receive the queries and route them through the cluster. > The most obvious candidate for "someone" is the developer and the > housekeeping stuff could be hidden in decorators. I wrote a bit more on > this at [1] (no working code yet, sorry). So when you change the number of databases in your cluster, do you also have to update *every* view in your application? You're making my case for me if that's so ;) -- "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 -~----------~----~----~----~------~----~------~--~---
