That's what I said.
Jim
"Mike Ault" <mikerault_at_earthlink.net> wrote in message
news:37fab3ab.0205061131.779ac9f0_at_posting.google.com...
> "Jim Kennedy" <kennedy-family_at_attbi.com> wrote in message
news:<rOwB8.238418$CH1.176607_at_sccrnsc02>...
> > function based index.
> > create index myIndex on dept(upper(loc));
> > then just have the sql do
> > select * from dept where loc like upper(:hvLocIn);
> > (:hvlocIn is the host variable.)
> > Jim
> > "Rudy Susanto" <rsusanto_at_atlas-sp.com> wrote in message
> > news:1a928d0b.0205060152.467b9d26_at_posting.google.com...
> > > Hi All,
> > >
> > > I need some suggestions about case sensitive implementation.
> > >
> > > SQL> select * from dept;
> > > DEPTNO DNAME LOC
> > > ---------- -------------- -------------
> > > 10 ACCOUNTING NEW YORK
> > > 20 RESEARCH DALLAS
> > > 30 SALES CHICAGO
> > > 40 OPERATIONS BOSTON
> > >
> > > SQL> select * from dept where loc='boston';
> > > no rows selected
> > >
> > > I realise that i have to modified the query according to the oracle
> > > way.
> > > I know about the oracle behavior but i don't know the good way to
> > > apply to the production.
> > > Right now we choose another database like oracle as our database but
> > > we have a little problem about case sensitive, as long as we use
> > > sqlserver we never met this problem.
> > >
> > > May be there are some tricks to solve this problem that i can apply:
> > > 1. create trigger to each table to convert every text into upper case,
> > > or
> > > 2. always use upper case on front-end to make sure the data in upper
> > > case
> > > 3. or the others
> > >
> > > As addition information we use clarion as our front-end.
> > >
> > > Is there a way to change the oracle setting that allow us ignore about
> > > the case sensitive? so we do not need to use the upper function.
> > >
> > >
> > > Thank in advance,
> > >
> > > Rudy Susanto
>
>
> How about just putting an upper function based index on the searched
columns?
>
> Mike
Received on Mon May 06 2002 - 21:08:37 CDT
