From oracle-l-bounce@freelists.org  Mon Aug  8 12:53:28 2005
Return-Path: <oracle-l-bounce@freelists.org>
Received: from air891.startdedicated.com (root@localhost)
 by orafaq.com (8.12.10/8.12.10) with ESMTP id j78HrSYZ003372
 for <oracle-l@orafaq.com>; Mon, 8 Aug 2005 12:53:28 -0500
X-ClientAddr: 206.53.239.180
Received: from turing.freelists.org (freelists-180.iquest.net [206.53.239.180])
 by air891.startdedicated.com (8.12.10/8.12.10) with ESMTP id j78HrQIP003343
 for <oracle-l@orafaq.com>; Mon, 8 Aug 2005 12:53:26 -0500
Received: from localhost (localhost [127.0.0.1])
 by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id DBCDD1DD389;
 Mon,  8 Aug 2005 12:53:23 -0500 (EST)
Received: from turing.freelists.org ([127.0.0.1])
 by localhost (turing [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id 18434-05; Mon, 8 Aug 2005 12:53:23 -0500 (EST)
Received: from turing (localhost [127.0.0.1])
 by turing.freelists.org (Avenir Technologies Mail Multiplex) with ESMTP id 5E5EB1DD2A3;
 Mon,  8 Aug 2005 12:53:23 -0500 (EST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references;
        b=TNkpM7jCvdEWeBVAMUiBOs5K9qN19SZBAbAM7HwwF8Kqj3ITA/ri2LrsBPfKEqEu2a6b+l7bE8XGX3/reqyNNhvd6nrqlsiE3sIAALu1OHLO4/fR2ceEL6Ncnpcxcvwr01rD3ubXqzKKsABAx6lmwZ4ARee4GLZEU6erQz/zCu8=
Message-ID: <de807caa0508081051396708cc@mail.gmail.com>
Date: Mon, 8 Aug 2005 12:51:31 -0500
From: Dennis Williams <oracledba.williams@gmail.com>
To: cemail_219@hotmail.com
Subject: Re: case sensitivity - database setting?
Cc: oracle-l@freelists.org
In-Reply-To: <BAY106-F43241C4B1B7493EDC7541A5B80@phx.gbl>
Mime-Version: 1.0
Content-Type: multipart/alternative; boundary="----=_Part_6763_11197332.1123523491475"
References: <BAY106-F43241C4B1B7493EDC7541A5B80@phx.gbl>
X-archive-position: 23573
X-ecartis-version: Ecartis v1.0.0
Sender: oracle-l-bounce@freelists.org
Errors-To: oracle-l-bounce@freelists.org
X-original-sender: oracledba.williams@gmail.com
Precedence: normal
Reply-To: oracledba.williams@gmail.com
X-list: oracle-l
X-Virus-Scanned: by amavisd-new-20030616-p9 (Debian) at avenirtech.net
X-mailscan-MailScanner-Information: Please contact the ISP for more information
X-mailscan-MailScanner: Found to be clean
X-MailScanner-From: oracle-l-bounce@freelists.org
X-Spam-Level: 
X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on 
 air891.startdedicated.com
X-Spam-Status: No, hits=-4.4 required=5.0 tests=AWL,BAYES_00,HTML_MESSAGE 
 autolearn=ham version=2.63
------=_Part_6763_11197332.1123523491475
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

J. Dex
 Others have addressed the situation where you are sorting the records. Wha=
t=20
I've seen is the situation where you are searching for a particular record.=
=20
You end up with the situation with=20
 WHERE UPPER('my search string') =3D UPPER(column)
As DBA, you can support this by creating a FBI (function-based index) on th=
e=20
column.
 The vendor must support this by including syntax such as the above in the=
=20
SQL they create. If the vendor doesn't support this syntax, then your only=
=20
alternative is to train your users to enter all data with a consistent case=
.
 Dennis Williams

 We are setting up an application (third-party out-of the-box type) and the
> group that is setting it up would like to set it up so that when users
> search for records the searches are NOT case sensitive.
>

------=_Part_6763_11197332.1123523491475
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

<div>J. Dex</div>
<div>&nbsp;</div>
<div>Others have addressed the situation where you are sorting the records.=
 What I've seen is the situation where you are searching for a particular r=
ecord. You end up with the situation with </div>
<div>&nbsp;&nbsp;&nbsp;&nbsp; WHERE UPPER('my search string') =3D UPPER(col=
umn)</div>
<div>As DBA, you can support this by creating a FBI (function-based index) =
on the column.</div>
<div>&nbsp;</div>
<div>The vendor must support this by including syntax such as the above in =
the SQL they create. If the vendor doesn't support this syntax, then your o=
nly alternative is to train your users to enter all data with a consistent =
case.
</div>
<div>&nbsp;</div>
<div>Dennis Williams<br><br>&nbsp;</div>
<div>
<blockquote class=3D"gmail_quote" style=3D"PADDING-LEFT: 1ex; MARGIN: 0px 0=
px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">We are setting up an application=
 (third-party out-of the-box type) and the<br>group that is setting it up w=
ould like to set it up so that when users
<br>search for records the searches are NOT case sensitive.<br></blockquote=
></div>

------=_Part_6763_11197332.1123523491475--
--
http://www.freelists.org/webpage/oracle-l

