RE: Case insensitive searches
- From: <rajendra.pande@xxxxxxx>
- To: <rjjanuary@xxxxxxxxxxxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
- Date: Tue, 18 Mar 2014 06:50:38 -0400
Would using regex be an option - of course I guess a lot will depend on
what kind of queries
But just wondering if you looked at regex.
-----Original Message-----
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of Ryan January
Sent: Monday, March 17, 2014 6:03 PM
To: oracle-l
Subject: Case insensitive searches
RHEL 5.10 / Oracle 11.2.0.3
This seems to be one of those classic situations that everyone runs
across at one time or another. We've been approached to assist in making
an existing in-house application's queries case insensitive. Many things
were discussed but the first option we're testing is NLS_SORT and
NLS_COMP changes. The settings remain default at the database level.
We've configured a login trigger to set NLS_SORT to BINARY_CI and
NLS_COMP to LINGUISTIC for sessions initiated by a particular user.
Less than a full day into testing we've already consistently run into
ORA 600's via Bug #15936924 (MOS 15936924.8). While it's sad to admit, I
really wasn't surprised. I expected to run into issues, but not this
soon in, and not this severe.
Where it goes from unfortunate to infuriating is that the planned fix is
to be included in 12.2 with no work around listed. The doc also
mentions 11.2.0.4 as being affected so there's no end in sight.
In light of this I think we need to take a step back and see how others
have approached these situations.
Having no plans to attempt a resolution on any announced time frame
leads me to believe Oracle simply doesn't have many users covering this
code path. Are these non-standard NLS settings really that out of the
norm? Has anyone else run across similar issues in the past? Did you
ever find a work around?
If you haven't run into this issue, how are you handling case
insensitivity mandates? Do you handle this in the app stack outside the
database? Do you change the data model and only store a standard case
inside the database? Do nothing outside of avert your eyes when you see
sql containing upper() on both sides of a predicate?
Any insight you can provide would be appreciated.
Thanks,
Ryan
--
------------------------------------------------------------------
This email is intended solely for the use of the addressee and may
contain information that is confidential, proprietary, or both.
If you receive this email in error please immediately notify the sender
and delete the email..
------------------------------------------------------------------
--
//www.freelists.org/webpage/oracle-l
Please visit our website at
http://financialservicesinc.ubs.com/wealth/E-maildisclaimer.html
for important disclosures and information about our e-mail
policies. For your protection, please do not transmit orders
or instructions by e-mail or include account numbers, Social
Security numbers, credit card numbers, passwords, or other
personal information.
--
//www.freelists.org/webpage/oracle-l
Other related posts:
