David,
Monday, January 28, 2002, 10:43:38 PM, you wrote:
DS> REALFROM: David Shields <d.shields@stripped>
DS> HOUR: 2002012901
DS> You wrote:
DS> What about mysqldump? See http://www.mysql.com/doc/m/y/mysqldump.html
DS> for more info about mysqldump.
DS> well, no, not really :
DS> site1 - has apache / php / mysql + database x
DS> site2 - has apache / php / mysql + database y
DS> site3 - has apache / php / mysql + database z
DS> at 9:00 am all databses (x,y,z) are same.
DS> during day, people at 1 update x, people at 2 update y, people at 3 update z.
DS> at (say) 23:00 , I want to put all x's changes into y and z, all y's
DS> changes into x and z, all z's changes into x and y.
mysqldump x > x.dmp
mysqldump y > y.dmp
mysqldump z > z.dmp
DS> would require that i then do a diff of x, y and apply all < diffs to x,
DS> all > diffs to y ... and so on - it looks like an over-engineered solution
DS> to me. What I was asking is whether replication would ease my pain.
I think, replication in any form is not a solution for you in this case.
You have to think hard what you want from the database and which data and what changes
should be done by various people on various databases.
That's a software design question, not MySQL's one.
Why don't you run all these sites using one MySQL server?
--
For technical support contracts, goto https://order.mysql.com/
This email is sponsored by Ensita.net http://www.ensita.net/
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Victoria Reznichenko
/ /|_/ / // /\ \/ /_/ / /__ Victoria.Reznichenko@stripped
/_/ /_/\_, /___/\___\_\___/ MySQL AB / Ensita.net
<___/ www.mysql.com
| Thread |
|---|
| • (Sort of ) replication issue | Victoria Reznichenko | 29 Jan |