If you're looking to load-balance the write requests... sorry, MySQL
replication won't help much (if at all).
Think about it... every insert/update/delete simply *has* to happen on
every server. You only *send* it to one of them, sure... but then it
replicates from that one to the other(s) and
Hi,
Jake Maul wrote:
*If 1/2 your tables are on server A and the other 1/2 are on server B,
then you've effectively split the read *and* write load between them.
How to do this without modifying the frontend is an exercise left to
the reader. :)
From what I've read in the past about MySQL
Daevid Vincent dae...@daevid.com wrote on 01/15/2009 09:57:19 PM:
you misunderstand me. I have three servers (dev, test, prod) that all
have maybe 3 databases EACH that have all these eventum* tables in them.
don't ask. a simple trickle won't do. I'm writing a script to loop
through them all.
I think you may be over-panicing. :-)
If you do a DROP on the master and that replicates through, just like the
create did, then you're all set.
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:
I'm having some difficulty getting my head around a particular query.
I'd like to make this a view once I get something working. However, all
I've been able to come up with uses a sub-query. So, no view on the horizon.
I have 3 tables:
users
id,
(etc. the usual)
disciplines
id,
name
