Re: HexDumped Binlogs
Posted by:
Rick James
Date: August 19, 2014 04:50PM
> Could it be enough to change the table definitions on the slave before dumping the data in?
_Maybe_. The problems are:
* It is hard enough to figure out how to get things 'right'. It is probably harder to get things consistently 'wrong'.
* You would be making more of a mess -- that would need to be cleaned up later.
Here's a _guess_ of what to do:
* Make sure the CREATE TABLEs say the same things on both Master and Slave
* Set some VARIABLE (character...) to latin1 to avoid utf8. This is the tricky part -- I'm not sure if it will work.
* Get a test environment with both Master and Slave. They could be on the same box if you use different "ports". I suggest M-S testing because the problem seems to come up in replication with utf8 somehow showing up. (latin1 and cp850 probably don't care as long as you are consistent; utf8 will complain because of unconvertible characters.)
Subject
Written By
Posted
Re: HexDumped Binlogs
August 19, 2014 04:50PM
September 05, 2014 05:52AM
September 06, 2014 08:12PM
September 06, 2014 08:14PM
September 15, 2014 08:58AM
September 16, 2014 11:17PM
Sorry, you can't reply to this topic. It has been closed.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.