From: Galen Boyer <galenboyer@yahoo.com>
Subject: Re: Case Insensitivity
Date: 2000/08/08
Message-ID: <ug0of94oo.fsf@yahoo.com>#1/1
Sender: gboyer@GBOYER
References: <8mnc45$oto$1@nnrp1.deja.com> <DjQj5.71717$3E6.720890@news1.alsv1.occa.home.com>
Content-Type: text/plain; charset=us-ascii
X-Abuse-Info: Otherwise we will be unable to process your complaint properly
X-Complaints-To: support@usenetserver.com
Organization: WebUseNet Corp  http://www.usenetserver.com - Home of the fastest NNTP servers on the Net.
User-Agent: Gnus/5.0803 (Gnus v5.8.3) Emacs/20.7
MIME-Version: 1.0
NNTP-Posting-Date: Tue, 08 Aug 2000 11:01:07 EDT
Newsgroups: comp.databases.oracle.server,comp.databases.oracle,comp.databases.oracle.misc


>>>>> "Kevin" == Kevin Lang <KLang@kevinlang.com> writes:

 Kevin> Hello, How is case insensitivity emulated in Oracle?  I
 Kevin> see that there are function-based indexes that would
 Kevin> allow me to index a mixed-case column as UPPER(colname),
 Kevin> and then use the "UPPER" function in the predicate, but I
 Kevin> can not get the optimizer to use that index.  A table
 Kevin> scan is always generated.  I have analyzed the table and
 Kevin> indexes updating the statistics, there are no NULLS, all
 Kevin> of the rules are followed.

Oracle will not use an index if you put a function around the
column.  It will basically say, all bets are off, cause you are
changing the data that I indexed on.

I use this functionality whenever I want a full-table scan
instead of the index.

where indexed.column + 0 = other.column
-- 
Galen Boyer


