On 8/28/2012 4:49 AM, Johan De Meersman wrote:
> Guess I'll be fixing it manually (well, sed is my friend) in a mysqldump before
> syncing up the second node after it's been upgraded.
There is another method you can use that doesn't require
dump+sed+restore. Convert the column from it's current type to BINARY
then back to the correct character set. This technique is described in
the old 4.1 manual when we first introduced character sets. Back then,
everyone was putting all sorts of data into latin1 fields and converting
it back on the client.
The example uses BLOB but BINARY will also work.
MySQL Principal Technical Support Engineer
Oracle USA, Inc. - Hardware and Software, Engineered to Work Together.
Office: Blountville, TN