Fulko Hew wrote:
I am using mySQL 3.22.4a-beta
yes, I know its old :-(
I have just stumbled across a problem with how it
treats 'uniqueness' in table contents.
I have a table with a column defined as:
create table test (name varchar(80) not null);
alter table test ADD UNIQUE
If you create your columns with the 'binary' parm (look in the manual),
then all the comparisons will be case-sensitive.
Can anyone either point out what I am doing wrong, or a workaround?
database, mysql, table
-
Bill Adams [EMAIL PROTECTED] replied:
Fulko Hew wrote:
I am using mySQL 3.22.4a-beta
yes, I know its old :-(
I have just stumbled across a problem with how it
treats 'uniqueness' in table contents.
I have a table with a column defined as:
create table test (name
12/11/2001 17:34:07, Fulko Hew [EMAIL PROTECTED] wrote:
I am using mySQL 3.22.4a-beta
yes, I know its old :-(
I have just stumbled across a problem with how it
treats 'uniqueness' in table contents.
I have a table with a column defined as:
create table test (name varchar(80) not null);
Giuseppe Maxia [EMAIL PROTECTED] responded:
The workaround is to use the attribute BINARY for your field
create table test (myfield varchar(80) BINARY not null, UNIQUE KEY myfield);
This way, the index is case sensitive.
Unfortunately, this feature was introduced in MySQL 3.23, so your
