why the current implement of replication is so difficult to make use of?
a few days recently, i though of mysql replication
and got an ideas....
---------
idea 1:
i leant it from IRC server
no "master" and "slave"
servers have equal rights
and specify 1 and only 1 server as REGISTER SERVER(may be named as id server)
all client update goto nearby server
and server judge if the QUERY is and UPDATE/INSERT or SELECT
for SELECT do locally
for UPDATE/INSERT, which care about "autoindex/primary key/unique index", do locally
else, send to REGISTER SERVER, and wait for result(error OR
last_insert_id())
this can solve "non conflicting KEY updates between the tables" problem
but still can't solve "update the sam rows on two servers"
------------------
idea 2:
i've lookup the mysql client library code
there's a code doing update/insert query AUTO redirect to master server
only SELECT done in slave server
but.. it's in CLIENT library
if we got application in binary release, how can we make use of replication?
"query auto redirect" should can be done in server, and we can do replication without
even recompiling source
------------------
do u guys have any other ideas ?
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
