Re: Case insensitive queries

From: Daniel Morgan <damorgan_at_x.washington.edu>
Date: Sat, 29 Nov 2003 08:41:36 -0800
Message-ID: <1070124126.317748@yasure>

Galen Boyer wrote:

> On Sat, 29 Nov 2003, forbrich_at_tyahoo.net wrote:
> 

>>Daniel Morgan wrote:
>>
>>>What is it you think Oracle is doing under the covers to make
>>>case insensitive queries possible? Give it some thought. There
>>>is no other way to compare byte values than to alter them. A
>>>switch in the init.ora does not change what is happening.
>>
>>But if it's done at the DB level, the developers can correctly
>>state that the performance issue is not theirs. Thereby
>>shedding their responsibility in the name of doing it 'at
>>internet speed'.
>>
>>(Lousy design is never a possible source of problems. Similar
>>to 'security? naw, no time now! we'll do it later, maybe in
>>production. shouldn't have an impact.')

> 
> 
> Please tell me any of this discussion has anything to do with
> lousy design?  This "lousy design" mantra is something thrown out
> by people to somehow let their argument have more merit.  Where
> is the lousy design in wanting Oracle to remove this limitation?
> 

Its a trap go back go back. ;-)

By which I mean your question is open-ended so no matter what anyone gives you as an example your response will be ... but I don't want to use it that way. So it would be preferable if you gave an example of somewhere that you think you need it and let us try to counter it. The one thing I will say is that in 14+ years working with Oracle I have never required a case insensitive string comparison within an application except when dealing with data from upstream systems that had not been cleaned up on import.

-- 
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 Sat Nov 29 2003 - 10:41:36 CST