Re: Case Sensitivity in select

From: <mdlcpgs_at_alpha.gns.cri.nz.nospam>
Date: Mon, 6 Sep 99 12:47:54 +1200
Message-ID: <7qv2v9$ai9$1@newshost.comnet.co.nz>

>None of these posts are addressing what is a real problem for people
>who are converting applications which generate hundreds of SQL queries
>against a database such as Access, which is case-insensitive, and now
>wish to port to Oracle. What do they do? Modify the entire application
>and lose indexing on tables due to using UPPER() or LOWER()??? When all
>that is needed is a simple parameter setting to tell Oracle to be case-
>insensitive?

I sympathize. I have never encountered the need to do a case-sensitive so wonder why Like operator works that way (apart from programmer laziness). However a case-insensitive switch in Oracle looks unlikely and a case-insensitive Like operator even more unlikely so back to the unideal world...

In your access application, you can deal with searches that are generated from forms. You use the On Filter and On Apply Filter events of a form to trap the WHERE clause it is going to use and then rewrite it. You generally need to do this anyway because of the stupid behaviour of combos (Lookup_ pseudo fields) and to be able to filter by subform. Its not trivial coding but it is possible. Received on Sun Sep 05 1999 - 19:47:54 CDT