Those refer _only_ to German 'ß' LATIN SMALL LETTER SHARP S. The example GF gave
did not involve that character.
To my knowledge, that is the only case where MySQL changed a collation after releasing it.
> -----Original Message-----
> From: Shawn Green [mailto:shawn.l.green@stripped]
> Sent: Friday, June 15, 2012 12:06 PM
> To: Rick James
> Cc: GF; mysql@stripped
> Subject: Re: Foreign key and uppercase / lowercase values
> On 6/15/2012 1:00 PM, Rick James wrote:
> > You are very close to a standalone test case. Please create such.
> Then post it on bugs.mysql.com .
> >> -----Original Message-----
> >> From: GF [mailto:ganfab@stripped]
> >> Sent: Friday, June 15, 2012 12:45 AM
> >> To: Rick James
> >> Cc: Shawn Green; mysql@stripped
> >> Subject: Re: Foreign key and uppercase / lowercase values
> >> I think the following might give complete information (I removed
> >> columns not involved in the problem)
> >> Server version: 5.1.49-3 (Debian)
> >> SET collation_connection = utf8_unicode_ci; Query OK, 0 rows
> >> ...
> Before he submits a test case, he should also review
> This has been a well-discussed problem both inside and outside the
> MySQL development processes.
> Shawn Green
> MySQL Principal Technical Support Engineer Oracle USA, Inc. - Hardware
> and Software, Engineered to Work Together.
> Office: Blountville, TN
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe: http://lists.mysql.com/mysql