RE: Master -> Slave/Master -> Slave problem.

2007-02-14 Thread Gary W. Smith
> Hi, > > on server B you need to set log-slave-updates to pass statements from A > over B to D. > > BTW: I can recommend you to use replicate-wild-do-table=db_name.* > instead of replicate-do-db, otherwise statements with db prefix before > tables won't replicate over B to D. RTM please > > >

RE: Master -> Slave/Master -> Slave problem.

2007-02-14 Thread Gary W. Smith
> You should have: > log-slave-updates > > on the slave/master host(s) > > > Best regards, > Irek Slonina Irek, Thanks for the follow up. Someone else has mentioned it but I just noticed that it was offlist.

Re: Master -> Slave/Master -> Slave problem.

2007-02-14 Thread Filip Krejci
Hi, on server B you need to set log-slave-updates to pass statements from A over B to D. BTW: I can recommend you to use replicate-wild-do-table=db_name.* instead of replicate-do-db, otherwise statements with db prefix before tables won't replicate over B to D. RTM please Filip I'm wor

Master -> Slave/Master -> Slave problem.

2007-02-13 Thread Gary W. Smith
I'm working with two distinct databases on four different boxes. Databases A on Server A needs to be present everywhere (Server B, C and D). Database B needs to be present on Server C. So I setup replication from Server A to Server B and Server D and then I setup replication from Server B to Serv