From: Rick James
Date: June 15 2012 7:19pm
Subject: RE: Foreign key and uppercase / lowercase values
List-Archive: http://lists.mysql.com/mysql/227682
Message-Id: <2E7DD7ADE53B044C8C8BCD9C5829E1EB1487607F5E@SP2-EX07VS01.ds.corp.yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Those refer _only_ to German '=DF' 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 afte=
r 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
>=20
> 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
> some
> >> columns not involved in the problem)
> >>
> >> Server version: 5.1.49-3 (Debian)
> >>
> >> SET collation_connection =3D utf8_unicode_ci; Query OK, 0 rows
> affected
> >> ...
>=20
> Before he submits a test case, he should also review
> http://bugs.mysql.com/bug.php?id=3D27877
> http://dev.mysql.com/doc/refman/5.5/en/news-5-5-21.html
>=20
> This has been a well-discussed problem both inside and outside the
> MySQL development processes.
>=20
> Regards,
> --
> Shawn Green
> MySQL Principal Technical Support Engineer Oracle USA, Inc. - Hardware
> and Software, Engineered to Work Together.
> Office: Blountville, TN
>=20
>=20
>=20
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe:    http://lists.mysql.com/mysql