Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion Case insensitive queries
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Galen Boyer  
View profile  
 More options Nov 28 2003, 8:23 pm
Newsgroups: comp.databases.oracle.server
From: Galen Boyer <galenbo...@hotpop.com>
Date: 28 Nov 2003 19:23:11 -0600
Local: Fri, Nov 28 2003 8:23 pm
Subject: Re: Case insensitive queries

On Fri, 28 Nov 2003, damor...@x.washington.edu wrote:
> Galen Boyer wrote:
>> 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.

How then should they get a case-insensitive query to execute?
Would you want them to do it the old-fashioned way..., and how
old-fashioned should it be?

> A properly designed application should force valid case for
> inserts and updates.

I would ask you to read my posting again.  I'm not asking the
database to somehow turn everything to a single case for storage
purposes or fix my very poorly designed DML strategies for me.
I'm talking about case-insensitive queries.  I am forced, because
of a limitation in Oracle, to either store a single-cased version
of all queriable columns used in searches, or I must explicitly
ask Oracle to function index a particular single-cased version
and then use that function in my search queries.

I would rather just be able to tell Oracle, hey, in this query,
ignore case and, btw, don't lose performance.

> Covering up for a bad design or bad implementation is not a
> good policy.

I just wish you would stop your bully-pulpit answers.  

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

What efforts are those and more valuable to whom?

--
Galen Boyer


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.