I see what you're saying. We have a replication chain, about 3
machines. Wouldn't
UPDATE db00.table set row = value where row = 'some_value';
break replication if db00 does not exist down the replication chain?
If so is there way around this?
2009/11/5 Rick James <rjames@stripped>:
> Look in SHOW SLAVE STATUS; and SHOW MASTER STATUS; (on appropriate
> machines) to see if there are any binlog/replicate-do/ignores. If so,
> then look for a USE before the UPDATE. When deciding whether to
> replicate and execute the statement, the USE is (confusingly) used
> instead of the actual tables referenced.
>
>
> Rick James
> MySQL Geeks - Consulting & Review
>
>> -----Original Message-----
>> From: Ariel [mailto:ariel@stripped]
>> Sent: Thursday, November 05, 2009 9:55 AM
>> To: replication@stripped
>> Subject: Re: UPDATE replication not working.
>>
>>
>> On Nov 5, 2009, at 12:46 PM, socomm@stripped wrote:
>>
>> > Hello all, a MySQL neophyte here. I've been handed a handful of
>> > MySQL servers to manage, and am having small problems with
>> > replication, which was setup by previous person in my
>> position. The
>> > replication works fine for the most part, however one of our
>> > developers came across a problem where he would UPDATE a table and
>> > it would not replicate to the slave. Everything works fine,
>> INSERT,
>> > CREATE, et cetera. Just UPDATE not replicating.
>> >
>> > Has anyone else come across this? All
>> help/suggestions/ideas welcomed.
>>
>>
>> What is the exact query that you are running? Are you using
>> Statement
>> or Mixed mode replication? What version of MySQL?
>> -a
>>
>> --
>> MySQL Replication Mailing List
>> For list archives: http://lists.mysql.com/replication
>> To unsubscribe:
>> http://lists.mysql.com/replication?unsub=1
>>
>
> --
> MySQL Replication Mailing List
> For list archives: http://lists.mysql.com/replication
> To unsubscribe: http://lists.mysql.com/replication?unsub=1
