db-derby-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sai Pullabhotla" <Sai.Pullabho...@jMethods.com>
Subject RE: Case-Insensitive Unique Constraint
Date Wed, 16 Jan 2008 17:48:18 GMT

Thanks Bryan. 

I thought about it. But I'm not sure if it is THE BEST way. Any other folks
here have any ideas/comments? 

Also, let us say, if we do go with two columns approach (one for Display
purpose and the other for storage purpose), is there a way I can set up
triggers on these tables to automatically put the lower/UPPER case values in
the internal column? I tried to create a BEFORE INSERT trigger, but did not
have any luck. I could not even get it to compile. 

Or do you think it is best to change the code where the INSERT and UPDATE
statements are, rather than messing with triggers? 

I appreciate any ideas/comments.


Sai Pullabhotla
jMethods, Inc. 
Phone: +1 (402) 408-5753 
Fax: +1 (402) 408-6861

-----Original Message-----
From: Bryan Pendleton [mailto:bpendleton@amberpoint.com] 
Sent: Tuesday, January 15, 2008 5:38 PM
To: Derby Discussion
Subject: Re: Case-Insensitive Unique Constraint

> Is there a way to create a unique constraint/index which ensures the
> uniqueness of data IGNORING the case? 

One idea would be to store the data twice, in two separate columns:
  - in one column, store the data normally, in the case as provided
  - in the other column, store the data in all upper case

Then create a unique index on the all-upper-case column.



View raw message