Hi. I am trying to set up a mysql replication master servers in a circular format in different geographical locations (Los Angeles, New York, Chicago, and Houston) but the client wants to keep working on the database and "catch up" with the rest of the offices should there ever be a network problem. I was thinking of designing the software to not allow the updates on the down node's tables in an INNODB transaction style so that each site can continue working on their datasets should there ever be a network problem and catch up when the network comes up. I was just wondering what are some downfalls on this idea?
Thank you. Scott Wong System Administrator --------------------------------------------------------------------- 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
