, June 15, 2012 12:45 AM
To: Rick James
Cc: Shawn Green; mysql@lists.mysql.com
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
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 = utf8_unicode_ci;
Query OK, 0 rows affected (0.00 sec)
show variables like '%colla%';
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 = utf8_unicode_ci; Query OK, 0 rows affected
(0.00 sec)
show variables like '%colla
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 = utf8_unicode_ci; Query OK, 0 rows affected
...
Before he submits
: Friday, June 15, 2012 12:06 PM
To: Rick James
Cc: GF; mysql@lists.mysql.com
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
On 6/15/2012 3:19 PM, Rick James wrote:
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.
Yes, it has been the only occurrence.
At 16.40 15/06/2012 -0400, Shawn Green wrote:
On 6/15/2012 3:19 PM, Rick James wrote:
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.
: Foreign key and uppercase / lowercase values
Good morning.
The application is Java.
The database version is : Server version: 5.1.49-3 (Debian)
This is an example of the problem:
__
mysql SET collation_connection = utf8_unicode_ci;
Query OK, 0 rows affected (0.00 sec
Good morning.
The application is Java.
The database version is : Server version: 5.1.49-3 (Debian)
This is an example of the problem:
__
mysql SET collation_connection = utf8_unicode_ci;
Query OK, 0 rows affected (0.00 sec)
mysql show variables like '%colla%';
Good morning,
I have an application where the user ids were stored lowercase.
Some batch import, in the user table some users stored a uppercase
id, and for some applicative logic, in other tables that have a
foreign key to the user table, their user ids are stored lowercase.
MySQL didn't throw
why are not using any where condition in the update statment
On Wed, May 16, 2012 at 1:24 PM, GF gan...@gmail.com wrote:
Good morning,
I have an application where the user ids were stored lowercase.
Some batch import, in the user table some users stored a uppercase
id, and for some
...
for further discussion.
Instead of changing the data, why not do the casefolding as you SELECT into
Java?
-Original Message-
From: Ananda Kumar [mailto:anan...@gmail.com]
Sent: Wednesday, May 16, 2012 3:43 AM
To: GF
Cc: mysql@lists.mysql.com
Subject: Re: Foreign key and uppercase / lowercase
Hello Ananda,
On 5/16/2012 6:42 AM, Ananda Kumar wrote:
why are not using any where condition in the update statment
WHERE clauses are not required. Performing a command without one will
affect ever row on the table.
On Wed, May 16, 2012 at 1:24 PM, GFgan...@gmail.com wrote:
Good
13 matches
Mail list logo