JB> As for database clustering, there's a philosophical issue here: Django
 JB> shouldn't need to know whether there's one database server behind it,
 JB> or five, or a hundred.

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.

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).

Footnotes: 
[1]  http://a.khavr.com/2007/10/01/how-to-use-mysql-replication-in-django/

-- 
Andrey V Khavryuchenko            
Django NewGate -  http://www.kds.com.ua/djiggit/
Chytach - http://www.chytach.com/

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to