On 11/24/05, Robert Cottrell <[EMAIL PROTECTED]> wrote: > I've been thinking about this as well, as our sites are now starting > to push the limits of a single MySQL database. > > I think, however, that the selection of master or slave database has > to persist for the entire page request or you risk inconsistent data > and transactions (even reads within a transaction can have locking > implications). Pages would probably need to be designated as read- > only or read-write and use the same throughout the page serve.
This is a critical point really. The entire request is either: * Read Only * Read Write The only problem I can see is with rendering components. What do we do with an action marked read_only which renders a component marked read_write? Leave it as an issue for users? Also, does mysql support multi master replication? Finally, does rails itself have to support this, or is it a candidate for a plugin? -- Cheers Koz _______________________________________________ Rails-core mailing list [EMAIL PROTECTED] http://lists.rubyonrails.org/mailman/listinfo/rails-core
