Re: Case insensitive queries

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.
>
> --
> Galen Boyer

Am I missing something obvious here?

Is there something here that can't be accomplished by creating a view on the underlying case-sensitive table(s), having a 'to_upper()' for the columns in question in the view, and encouraging the app developer to do an implicit 'to_upper()' on the request?

Even for update situations, an inline view based on the above view should manage to handle most situations, shouldn't it?

If I am missing something, I am perfectly willing to retract my opinion. The opinion is based on many developers I have met not being able or willing to learn the underlying capability of the RDBMS (not just Oracle), and therefore doing things very stupidly - eg: creating a PL/SQL or T-SQL loop when a simple, properly projected, select would do the trick. Received on Fri Nov 28 2003 - 14:17:30 CST