On 3/14/01, 6:59:18 PM, Shaw Terwilliger <[EMAIL PROTECTED]> wrote
regarding [GENERAL] Case Insensitive CHECK CONSTRAINTs:
> I have a table with a TEXT field called "username". I'd like to retain
the
> case of the data stored here, but I'd like all comparisons to be done
without
> regard to case. Since all these accesses _should_ be done through
database
> functions, I can simply lower() the input values and compare. I also
have
> an index created on lower(username), so lookups are quick.
> However, I'd also like to have some sort of table constraint to make sure
> alternate case "duplicate" records don't creep into the table. Any tips?
As long as you have a UNIQUE index on lower(username) that will prevent
"duplicate"s. The UNIQUE applies to the index entry not the column(s) the
index applies to.
- Richard Huxton
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
