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 cur
e-
> From: Johan De Meersman [mailto:vegiv...@tuxera.be]
> Sent: Tuesday, August 28, 2012 1:49 AM
> To: Rick James
> Cc: mysql
> Subject: Re: MySQL, UTF8 and collations
>
> - Original Message -
> > From: "Rick James"
> >
> > There is a
- Original Message -
> From: "Rick James"
>
> There is a section on German Sharp-s in
> http://mysql.rjweb.org/doc.php/charcoll
> I agree with "dirty".
Yes, seen it, but thank you. I'm not having character set issues, everything is
nicely UTF8. I'm merely running into the scheiße bug,
Eventually they said "Oh, let's add another, compatible, collation".
They were caught between a rock and a hard place.
> -Original Message-
> From: Johan De Meersman [mailto:vegiv...@tuxera.be]
> Sent: Monday, August 27, 2012 7:43 AM
> To: mysql
> Subject: MySQ
Hey,
We're upgrading MySQLs from 5.0 to 5.5, and running into the predictable
utf8_general_ci bu^Wwe-meant-to-do-that with german ß and similar characters.
The server swallowed the existing datafiles (thank god for that) so we're up
and running, but "check table" does whine about needing a ful
