Hi Zahir!
Setting NLS_COMP to "linguistic" will also entail using function and
will have just the same cost as the functional index. I don't see the
problem with the functional indices or Oracle*Text. If, for some reason,
Oracle*Text is not good enough, there are always things like Lucene or
Sphinx. There are also other tricks: having a computed column and then
indexing it with a normal index. If push comes to shave, it is possible
to create post insert or update trigger which would fill an additional
real column with lower(original column), which would do case insensitive
search at the expense of some space. Every method of the case
insensitive search would have to use function to bring the string to a
uniform case, in order to perform case-insensitive search. The only
choice you have is when to invoke the function. You can invoke it during
the search itself or at the point of inserting/updating the row.
Regards
On 04/04/2018 12:19 PM, Zahir Mohideen wrote:
You can set the nls settings , perform the case insensitive search.
http://mfzahirdba.blogspot.com/2010/04/case-sensitiveness.html
- Zahir
Zahir Mohideen
http://mfzahirdba.blogspot.com/
/Nothing so *GREAT *was achieved without enthusiasm/
On Tue, Apr 3, 2018 at 5:36 PM, Mladen Gogala <gogala.mladen@xxxxxxxxx <mailto:gogala.mladen@xxxxxxxxx>> wrote:
Better how? What aspect of case insensitive search needs improvement?
On 04/03/2018 11:37 AM, Sanjay Mishra (Redacted sender smishra_97
for DMARC) wrote:
Is there any good solution for Case insensitive search to one or
two col level on table ? Is any new featured added in any 12c
flavor that provide better solution over old Index/Function based
Index/Context index ?
TIA
Sanjay
-- Mladen Gogala
Database Consultant
Tel: (347) 321-1217
