utf8 : utf8_general_ci O=o=Ò=Ó=Ô=Õ=Ö=ò=ó=ô=õ=ö oe oz
utf8 : utf8_general_mysql500_ci
utf8 : utf8_danish_ci O=o=º=Ò=Ó=Ô=Õ=ò=ó=ô=õ oe=Œ=œ oz
utf8 : utf8_swedish_ci
utf8 : utf8_estonian_ci O=o=º=Ò=tf8_unicode_ci
O=o=º=Ò=Ó=Ô=Õ=Ö=ò=ó=ô=õ=ö oe=Œ=œ oz Ø=ø
utf8 : utf8_polish_ci
O=o=º=Ò=Ô=Õ=Ö=ò=ô=õ=ö oe=Œ=œ oz Ó=ó Ø=ø
utf8 : utf8_spanish_ci
oe=Œ=œ oz Ø=ø
utf8 : utf8_spanish2_ci O=o=º=Ò=Ó=Ô=Õ=Ö=ò=ó=ô=õ=ö
oe=Œ=œ oz Ø=ø
As I understand it, the oe ligature collates as it it were the two letters "oe" for most utf8 collations. However for utf8_general*, it collates after Z:
utf8_general_ci X=x Y=y=Ý=ý=ÿ=Ÿ yz Z=z=Ž=ž zh zz Æ=æ Ð=ð Ø=ø Þ=þ Ł=ł
Œ=œ ƒ Ǉ=ǈ=ǉ
utf8_general_mysql500_ci X=x Y=y=Ý=ý=ÿ=Ÿ yz Z=z=Ž=ž zh zz Æ=æ Ð=ð Ø=ø Þ=þ
ß Ł=ł Œ=œ ƒ Ǉ=ǈ=ǉ
Is this what you mean by "barfs"?
> -----Original Message-----
> From: Johan De Meersman [mailto:vegivamp@stripped]
> Sent: Tuesday, August 28, 2012 1:49 AM
> To: Rick James
> Cc: mysql
> Subject: Re: MySQL, UTF8 and collations
> ----- Original Message -----
> > From: "Rick James" <firstname.lastname@example.org>
> > 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, but
> while utf8_unicode_ci does properly handle that, it stil barfs on cœr
> (that's oe in one character) and I'm wondering why.
> > As I understand it, about 5.1.24, they said "Oops, sharp-s is
> > wrong, let's fix it". The fix broke things, but they stuck by the
> > "correct" sorting. Eventually they said "Oh, let's add another,
> > compatible, collation".
> > They were caught between a rock and a hard place.
> The hard place being having to go "oops, sorry we broke things, we
> reverted the change and will introduce a new default collation in the
> next version"? Yes, poor software vendors, why do people always expect
> them to admit they made a mistake in judgement.
> And, of course, "alter table foo collate utf8_general_mysql500_ci"
> doesn't do what you hope, either. It changes the table's default
> collation nicely, and then explicitly adds the *old* collation to all
> the rows you were hoping to have fixed.
> 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.
> Linux Bier Wanderung 2012, now also available in Belgium!
> August, 12 to 19, Diksmuide, Belgium - http://lbw2012.tuxera.be