Re: Case insensitive queries

Galen Boyer wrote:

> On Fri, 28 Nov 2003, damorgan_at_x.washington.edu wrote:
>
>

>>Give it some thought. 

Didn't mean to be.

   All Oracle needs to do
> is give the DBA a switch at the column level to allow for this
> particular column to have this case insensitivity on queries.
> Allow for it to be altered. This would be quite akin to
> materialized views. I bet this is how 10g ends up implementing
> it.

I have 10g and I would bet you are incorrect.

   Yes, the developers and dbas wouldn't be devoid of
> maintenance of these objects, but the setup, creation, ongoing
> insertions? All handled by the database.
>
> I'm going to look back and see if I can find any post where you
> got all uppity about materialized views when they came on the
> scene.

You'll fail. They, too, provide real value.

   Wouldn't surprise me to find a few. I bet you got all up
> in arms about select auditing. How bout VPD? Where you all
> pissed off about java in the database? Lets turn the tables.
> Did you get all pissed off at locally managed tablespaces?

Only Java and only because it is slow compared to PL/SQL. I would have prefered a built-in package to make identical functionality available without the additional language. But none of them are, IMO, a kludge for a data integrity related design problem. Simply stated if two things are going to be compared they should be identical.

This isn't a big emotional issue with me and given the number of posts to this thread I think this has gotten out of hand so if you wish to respond to this please choose just one or lets communicate off-line.

-- 
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)