Re: Case insensitive queries

From: Daniel Morgan <damorgan_at_x.washington.edu>
Date: Fri, 28 Nov 2003 10:48:03 -0800
Message-ID: <1070045315.606163@yasure>

Galen Boyer wrote:

> On Sun, 23 Nov 2003, forbrich_at_yahoo.net wrote:
>
>

>>(Seems to me the requirement for case-insensitivity would be a
>>generated by programmer laziness or insufficient user training
>>- not uncommon these days.)

>
>
> Why is it that when Oracle has an obvious limitation, people
> respond like this? The web is pretty much a case-insensitive
> world. Oracle crows about being all "webified" but it doesn't
> offer this simple feature. Sure, the data is case-sensitive, but
> it would be damn nice for the database to allow the developer the
> ability to turn it off or on based on query needs.

I disagree completely. When 10g is released I will advise my students to never use the option for case insensitive queries.

A properly designed application should force valid case for inserts and updates. Covering up for a bad design or bad implementation is not a good policy. It is only one step removed from making all searches using the SOUNDEX function or making all columns VARCHAR2(4000).

So is it a limitation? Absolutely. Is it one I am glad Oracle has remedied? No! Efforts put elsewhere would have been far more valuable.

-- 
Daniel Morgan
http://www.outreach.washington.edu/ext/certificates/oad/oad_crs.asp
http://www.outreach.washington.edu/ext/certificates/aoa/aoa_crs.asp
damorgan_at_x.washington.edu
(replace 'x' with a 'u' to reply)

Received on Fri Nov 28 2003 - 12:48:03 CST