Case Insensitive search and "IN" Clause - Open SQL

Hi,
I have some doubts regarding Open SQL:
Is there any support for Case Insensitive Search in Open SQL, is it availabe by default?
Is there any restriction on number of elements in "IN" Clause, in Open SQL, is there any default number?
I have checked the [Open SQL Grammer|http://help.sap.com/saphelp_nwce711/helpdata/en/9b/f46cabaa874bc9a82234e8cf1d0696/frameset.htm] also, but nothing found there.
Thanks,
Piyush
P.S I didn't find any other appropriate place to post this thread, let me know the correct categorization of Open SQL in case its wrong.

Is there any support for Case Insensitive Search in Open SQL, is it availabe by default?
When you are querying any strings, it is always case sensitive.
Is there any restriction on number of elements in "IN" Clause, in Open SQL, is there any default number?
I don't think there area any. IN opearator works like combined ORs and here you don't have any restrictions in fields number.
Regards
Marcin

Similar Messages

Case insensitive search and "IN" Clause in Open SQL

Hi,
I have some doubts regarding Open SQL:
- Is there any support for Case Insensitive Search in Open SQL, is it availabe by default?
- Is there any restriction on number of elements in "IN" Clause, in Open SQL, is there any default number?
I have checked the [Open SQL Grammer |http://help.sap.com/saphelp_nwce711/helpdata/en/9b/f46cabaa874bc9a82234e8cf1d0696/frameset.htm]also, but nothing found there.
Thanks,
Piyush
P.S I didn't find any other appropriate place to post this thread, let me know the correct categorization of Open SQL in case its wrong.

> I have some doubts regarding Open SQL:
I believe that you've questions and not doubts...
> - Is there any support for Case Insensitive Search in Open SQL, is it availabe by default?
Nope, there is nothing like that. By default all supported database use a bytewise equal operator - case insensitivness needs to be programmed by hand.
E.G. using UPPER(x)/LOWER(x) functions.
Be aware that this disables the possibilities of index usage.
> - Is there any restriction on number of elements in "IN" Clause, in Open SQL, is there any default number?
Yes, there is a restriction and it differes between the different DBMS.
Until recently you could have 2000 variables per statement with MaxDB.
The current versions of DBSL and MaxDB Kernel now support up to 10000 variables per statement.
Anyhow, in most cases, such a long in list can and should be avoided by using the FOR ALL ENTRIES construct. With this, the DBSL automatically splits the long IN list into smaller chunks and executes the statements several times.
This is invisible to the ABAP report - it just gets the result set as usual.
> P.S I didn't find any other appropriate place to post this thread, let me know the correct categorization of Open SQL in case its wrong.
I guess in anyone of the DB forums is Ok.
regards,
Lars

Support for Case Insensitive Search and IN Clause in Open SQL

Hi,
I have some doubts regarding Open SQL:
- Is there any support for Case Insensitive Search in Open SQL, is it availabe by default?
- Is there any restriction on number of elements in "IN" Clause, in Open SQL, is there any default number?
I have checked the [Open SQL Grammer |http://help.sap.com/saphelp_nwce711/helpdata/en/9b/f46cabaa874bc9a82234e8cf1d0696/frameset.htm]also, but nothing found there.
Thanks,
Piyush
P.S I didn't find any other appropriate place to post this thread, let me know the correct categorization of Open SQL in case its wrong.

No cross posting.
Read the "Rules of Engagement"
Regards
Juan

Case insensitive search and replace using ASP and Oracle database

I am interested in providing a case insensitive search and replace query in a Active server page. At present data is collected from a html form which passes the text values to a ASP page. The ASP page runs a search (select query) to find if the data is already in the Oracle database, if it isn't the ASP page runs sql (INSERT) to insert the record, if not the page returns a form indicating that the record already exists. At present we can convert the case of new records using the VB UCase() function. But can't do a insensitive search with the existing records. *The Query must be able to utilize ASP variables.
Any help would be much appreciated.
David Cheryk
null

I can't check your script right now since I'm not on Mac. I recommend you to use FindChangeByList script for CS4 instead (it works with CS3): http://forums.adobe.com/servlet/JiveServlet/download/2080627-12695/FindChangeByListCS4.zip together with Martin Fisher's: http://www.kasyan.ho.com.ua/downloads/RecordFindChange_CS3_Kas.zip
Use this script to record settings from Text and GREP tabs, then copy and paste them into FindChandgeList.txt file.
Or, optionally you can use this script: http://www.kasyan.ho.com.ua/find_change_by_queries.html.
Kasyan

Case insensitive search and index

I have to execute a case insentitive search.
I created this index on a not null field:
create index indx_prova on
table (nlssort(campo, 'NLS_SORT=BINARY_CI'));
The select is:
select * from tabella where campo like 'A storage%'
This select should retrive 5 records:
A storage ring for crystalline beam studies
a storage ring for crystalline beam studies
A Storage Ring for Crystalline Beam Studies
A storage ring for crystalline beam studies
A storage ring for crystalline beam studies
Instead I got only 3 records:
A storage ring for crystalline beam studies
A storage ring for crystalline beam studies
A storage ring for crystalline beam studies
So The query isn't case insensitive.
I can't set nls_sort=BINARY_CI and nls_comp=LINGUISTIC at level session.
Is there a solution.
Am I doing something wrog?

I set alter session set nls_comp=LINGUISTIC; alter session set nls_sort=BINARY_CI;
I create this index:
create index titolo_indx on
table (nlssort(campo, 'NLS_SORT=BINARY_CI'));
If I execute this query:
select * from ri01_prodotti where titolo like 'A storage ring f%'
Oracle doesn't user the index.
SQL_ID 7yvspnyf96vp8, child number 0
select * from ri01_prodotti where titolo like 'A storage ring%'
Plan hash value: 350479533
| Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time |
| 0 | SELECT STATEMENT | | | | 2020 (100)| |
|* 1 | TABLE ACCESS FULL| TABLE | 1 | 1365 | 2020 (1)| 00:00:25 |
Predicate Information (identified by operation id):
1 - filter("CAMPO" LIKE 'A storage ring%')
If I execute a query with =, oracle use index.
select * from table where campo ='A storage ring for crystalline beam studies'
SQL_ID 5jzr5nm6b37pq, child number 0
select * from ri01_prodotti where titolo ='A storage ring for crystalline beam
studies'
Plan hash value: 3866031381
| Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time |
| 0 | SELECT STATEMENT | | | | 151 (100)| |
| 1 | TABLE ACCESS BY INDEX ROWID| RI01_PRODOTTI | 377 | 502K| 151 (0)| 00:00:02 |
|* 2 | INDEX RANGE SCAN | TITOLO_INDX | 151 | | 3 (0)| 00:00:01 |
Predicate Information (identified by operation id):
2 - access("RI01_PRODOTTI"."SYS_NC00078$"=HEXTORAW('612073746F726167652072696E6720
666F72206372797374616C6C696E65206265616D207374756469657300') )

Case Insensitive Search coupled with "LIKE" operator.

Greetings All, I am running Oracle 11gR1 RAC patchet 25 on Windows X64.
This db supports and application that requires case insensitive searches.
Because there are a few entry points into the db I created an "after login" trigger:
CREATE OR REPLACE TRIGGER MyAppAfterLogon_TRGR
AFTER LOGON
ON DATABASE
DECLARE
vDDL VARCHAR2(200) := 'alter session set nls_comp=''linguistic''';
vDDL2 VARCHAR2(200) := 'alter session set nls_sort=''binary_ci''';
BEGIN
IF ((USER = 'MyAppUSER') OR(USER = 'MyAppREPORTINGUSER')) THEN
EXECUTE IMMEDIATE vDDL;
EXECUTE IMMEDIATE vDDL2;
END IF;
END MyAppAfterLogon_TRGR;
This ensures that everyone connecting to the DB via any mechanism will automatically have case insensitive searches.
Now, to optimize the know queries I created the standard index to support normal matching queries:
select * from MyTable where Name = 'STEVE';
The index looks like:
CREATE INDEX "CONTACT_IDX3 ON MYTABLE (NLSSORT("NAME",'nls_sort=''BINARY_CI'''))
This all works fine, no issues.
The problem is when I write a query that uses the "LIKE" operator:
select * from MyTable where Name like 'STEV%';
I get back the record set I expect. However, my index is not used? I can't for the life of me get this query to use an index.
The table has about 600,000 rows and I have run gather schema stats.
Does anyone know of any issues with case insensitive searches and the "LIKE" clause?
Any and all help would be appreciated.
L

I think there is issue with your logon trigger :
"IF ((USER = 'MyAppUSER') OR(USER = 'MyAppREPORTINGUSER')) THEN"
it should be :
IF UPPER(USER) = 'MYAPPUSER' OR UPPER(USER) = 'MYAPPREPORTINGUSER' THEN
because user name stored in Upper case. Check and try.
HTH
Girish Sharma

Phonetic and case insensitive searches in Oracle

Hi,
Do you know if Oracle 9i allows phonetic searches ? I've found several solutions for case insensitive searches, but I'd need phonetic searches too (like 'había' vs. 'havia' vs. 'habia', etc)
Any comment would be really welcome.
Thanks in advance,
Juan

lookup soundex in the SQL Reference guide.

Error in a report after enabling case insensitive search in conn pool prop

Hi All,
I put the below code in connection pool's connection string to enable case insensitive search.
alter session set NLS_SORT=BINARY_CI
alter session set NLS_COMP=LINGUISTIC
After putting this code one of my report started giving the below error which was working fine otherwise.
Error Codes: OPR4ONWY:U9IM8TAC:OI2DL65P
State: HY000. Code: 10058. NQODBC SQL_STATE: HY000 nQSError: 10058 A general error has occurred. nQSError: 16001 ODBC error state: S1000 code: 1791 message: OracleODBCOraORA-01791: not a SELECTed expression. nQSError: 16001 ODBC error state: S1000 code: 1791 message: OracleODBCOraORA-01791: not a SELECTed expression. nQSError: 16015 SQL statement execution failed. (HY000)
The report gives error for the below divide condition when I select a column from a different dimension (eg: region)
COUNT(DISTINCT RMA.RMA)/COUNT(DISTINCT User."User Name")
Can anyone please throw a light why this is happening.

Below is the SQL which is throwing error in OBIEE. It was working fine when I tried running it in toad:
select T1609.ATTRIB_05 as c1,
count(distinct T1609.ATTRIB_42) as c2,
TRUNC(T1159.FSCL_WEEK_START_DT) as c3
from
WC_DAY_D T1159 /* RMA_RECEIVED_DT(WC_DAY_D) */ ,
WC_RMA_D T571,
WC_FV_FA_D T1609,
WC_FV_FA_F T1679
where ( T571.ROW_WID = T1679.RMA_WID and T1159.ROW_WID = T1679.RMA_RECEIVED_WID and T1609.ROW_WID = T1679.FV_FA_WID and T1609.ATTRIB_39 <> 'FV' and (T571.STATUS_CD in ('2nd FA', '2nd FA Review', 'Closed')) and TRUNC(T1609.TODO_ACTL_END_DT) is not null and TRUNC(T1159.FSCL_WEEK_START_DT) between TIMESTAMP '2009-03-22 00:00:00' and TIMESTAMP '2009-04-12 00:00:00' )
group by T1609.ATTRIB_05, TRUNC(T1159.FSCL_WEEK_START_DT)
order by c3
-------------------- Query Status: Query Failed: [nQSError: 16001] ODBC error state: S1000 code: 1791 message: [Oracle][ODBC][Ora]ORA-01791: not a SELECTed expression.
[nQSError: 16001] ODBC error state: S1000 code: 1791 message: [Oracle][ODBC][Ora]ORA-01791: not a SELECTed expression.
[nQSError: 16015] SQL statement execution failed.

Case insensitive search working in dev but not in prod

Hello All,
I had set the CASE_SENSITIVE_CHARACTER_COMPARISON parameter as OFF in NQSConfig.ini file for enabling the case insensitive search in OBIEE.
This setup is letting me do the case insensitive search in Dev env but the same doesnt work in prod env. I tried pointing both prod and dev rpd to same prod db.
With same db also, case insensitive search doesnt work in prod env.
Any idea for which other configuration I can look for.
Thanks in advance.

Thanks Stijin. I had seen this post earlier. Case insensitive search works fine after setting the value for NLS_SORT and NLS_COMP in production RPD but the other report with distinct clause starts failing. Not sure about the reason.
Saw this comment from you in that post:
The only compromise solution we could find was to "cache" the column value we wanted to use in insensitive searches. These were mainly used in "show all choices" while setting prompts. Other than that there isn't much you can do in an Oracle database.
Can you please tell me how to implement the above.

Case-insensitive Search with Search Form

I am using a Search Form with a UIX Page. One of the issue that need to be resolved is to be able to do case-insensitive search for text information stored in some database columns. Please advise me how to implement case_insensitive search with JDeveloper's Search Form.
Thanks in advance,

Hi Qian,
This article (below) by Steve Muench explains how you can customize Query by example behaviour of ADF BCs and if you really want, how to create your own ViewCriteriaAdapter (but you don't have to go quite that far - luckily :) ).
http://radio.weblogs.com/0118231/2005/02/10.html#a492
Here is what I did. I implemented the following method in my base view object class (MyBaseViewObject). Note that this code is based on a piece of code that Steve posted on his blog (http://radio.weblogs.com/0118231/stories/2003/07/11/implementingAViewCriteriaAdapterToCustomizeQueryByExampleFunctionality.html); originally an example about creating your own ViewCriteriaAdapter.
Since applyViewCriteria(oracle.jbo.ViewCriteria) is used by the query-by-example mechanism you're able to "intercept" the ViewCriteria on "it's way in". After that the standard ViewCriteria does it's job as ususal and generated the where clause when required.
public void applyViewCriteria(ViewCriteria vc)
     if( null == vc || vc.size() == 0 ) super.applyViewCriteria(vc);
     ViewCriteriaRow criteriaRow = (ViewCriteriaRow)vc.first();
     StructureDef def = criteriaRow.getStructureDef();
     AttributeDef[] attrs = def.getAttributeDefs();
     System.out.println(getClass().getName() + ": applyViewCriteria()");
     boolean bFirst = true;
     do{
       if(vc.hasNext() && !bFirst) criteriaRow = (ViewCriteriaRow)vc.next();
       criteriaRow.setUpperColumns(true);
       for (int j = 0, attrCt = attrs.length; j < attrCt; j++)
         String criteriaAttrVal = ((String)criteriaRow.getAttribute(j));
         if (criteriaAttrVal != null && !criteriaAttrVal.equals("") && !JboTypeMap.isNumericType(attrs[j].getSQLType()))
          criteriaRow.setAttribute(j,criteriaAttrVal.toUpperCase());
       bFirst=false;
     }while(vc.hasNext());
     super.applyViewCriteria(vc);
NOTE that doing this makes all your views case insensitive (to vc search) you may want to implement more functionality in your base view object to set whether a view is in case insensitive mode or not.
ALSO that flag will not be passivated (if I remember correctly - someone correct me if I'm wrong) so you'll have to add that flag to the passivated data.
Cheers!
Sacha

Case-insensitive searches on lob

Hi,
I work with oracle 10 on linux.
I have a table with clob.
I need to do case-insensitive searches on this field.
How can I do? I can't use upper or lower function.

Yes, you can :
SQL> desc PS_RC_SOL_PRODSRCH
Name                                      Null?    Type
SETID                                     NOT NULL VARCHAR2(5 CHAR)
SOLUTION_ID                               NOT NULL NUMBER(15)
PROD_DESCRLONG                                     CLOB
SQL> select setid,PROD_DESCRLONG
2 from   PS_RC_SOL_PRODSRCH
3 where dbms_lob.instr(lower(PROD_DESCRLONG),'n') > 0
4 and   rownum<3;
SETID
PROD_DESCRLONG
NLCOM
|NLC0001|Benefits|
NLCOM
|NLC0001|Benefits|Nicolas.

GetOrdinal of AseDataReader Class is not doing case-insensitive search

hi,
I am working on 12.5.4 version of sybase ASE.I am using 'Sybase.AdoNet2.AseClient.dll' to connect with database. I am using GetOrdinal method of ASEDatareader class (that as per documentation performs a case-sensitive lookup first. If it fails , a second search that is case-insensitive occurs) but in my case it is not performing case-insensitive search. I am attaching the document for your reference.
http://infocenter.sybase.com/help/index.jsp?topic=/com.infocenter.dc20066.1570100/doc/html/san1364409576274.html
Thanks,
Raman

Hi Monica,
Another thing you want to make sure is on your ASE that the oledb/adonet MDA scripts are up to snuff. Some of our fixes in the driver are in this.
If you login into the ASE and get the output of sp_version.
You should get something like this:
OLEDB MDA Scripts
         15.7.0.1250.1013/Wed Feb 19 UTC 00:28:47 2014
The ado.net driver and the older oledb driver use some specific MDA scripts on the ASE.
Read the coverletter of the SDK (Software Developers Kit for ASE). It explains how to update the MDA scripts. They are on the client side $sybase\ADONET\sp.
So where you downloaded the SDK you want to click Info then look for the README.
This is all the SDKs:
* Updating the metadata stored procedures required by ODBC, OLE DB and
jConnect Drivers on Adaptive Server Enterprise
Certain new features and bug fixes in ODBC, OLE DB and jConnect drivers
require you to modify the metadata stored procedures in Adaptive Server.
These stored procedures may not be up-to-date on your host ASE server due
to various reasons.
If the metadata stored procedures are outdated, you may not be able to use
some of the fixes that are implemented in this SP/ESD, so you will need to
manually install the updated metadata stored procedures.
To update the metadata stored procedures in Adaptive Server, first determine
the version of the meta-data scripts installed on the ASE. To do so, execute
the following command:
sp_version
go
The version number of the ODBC, OLE DB and jConnect meta-data scripts will
be displayed.
Review the version number column and compare it against the version of the
driver being used.
If the metadata scripts are outdated, the version installed will be older
than the driver build number or you will encounter one of the following:
- stored procedure sp_version is not found
- the stored procedure output does not print a row for the driver
The updated scripts are included with the drivers and can be installed as
follows:
For ODBC & OLE DB:
- Go the "sp" directory under the ODBC/OLE DB installation directory
- Execute the install_odbc_sprocs script for the ODBC Driver and
install_oledb_sprocs script for OLE DB Provider.
Syntax for using the script is:
        install_[odbc/olebd]_sprocs <ServerName> <username> [<password>]
         where <ServerName> is the name of the Adaptive Server
             <username> is the username to connect to the server
             [<password>] is the password the username
             (don’t supply this for null password)
For jConnect:
- Go to the "sp" directory under the jConnect installation directory. Based
on your host ASE server version, choose the appropriate SQL script.
- Use isql or another tool of your choice to execute the selected script.
This will install the current meta-data stored procedures.
Thanks,
Dawn

Case insensitive searching in Interactive Page

Hi all,
I am currently working on the interactive report, and wondering is it possible to perform case insensitive search for the data in the textbox besides the magnifying class.
By the default, the system uses "=" for searching. I tried the searching option using "contains", and it would be able to search the content in uppercase and lower case scenario. Is it possible to make "contains" as the default?
Thanks,
Thomas.

By the default, the system uses "=" for searching.I get "Row text contains..." as the filter when entering text directly into the default search box. Perhaps you are working with a saved report?
There's a way to make all IR comparisons case insensitive. See this <a ref="http://apex.oracle.com/pls/otn/f?p=34839:18">example of case/accent insensitive search</a> on a standard report.
That code can't be put in a Before Regions process as described to work with IRs as page processes are not executed by the AJAX call that refreshes the report. However, IR refreshes do run the Virtual Private Database PL/SQL call defined in the application security attributes, so putting the NLS modification code there will work.
Go to Application > Shared Components > Edit Security Attribute | Virtual Private Database (VPD), and make the call from there. Due to the specific requirements of the code that has to be called from here when used for security purposes, this is probably best done by setting this up to make separate calls to packages defined outside APEX, one to handle any actual VPD and other security-related details, and others to orchestrate any other code that has to be run. (For example, in this case it may not be desired to alter the NLS environment on every page, so the program could take a parameter specifying the current page and apply the ALTER SESSION conditionally on this.)

Possible to do case-insensitive searches?

G'day,
I was wondering if it's possible to do case-insensitive searches in oracle/HTMLDB?
I've tried what I thought would work
"select * from application where name like '%microsoft%'", this unfortunately doesn't return any records with a capital in it(eg "Microsoft").
If there is no way to do case-insensitive searches what is the best way around it?
Thanks
-Colin

Colin,
Yes it is possible to do case insensitive searches using SQL. Try, for example:
select * from application where upper(name) like '%ORACLE%'
The trick is to upper() both sides of the like operator.
Sergio

Case insensitive search on subject name to retrieve a certificate from key chain.

Hi,
I need to find the client certificate from key chain based on the subject name.
Currently, I am using attribute kSecLabelItemAttr and providing the subject name to create the attribute list for the API "SecKeychainSearchCreateFromAttributes" which gives the certificate.
Problem: This certificate search is case sensitive for the subject name.
Question: Is there a way to do a case insensitive search on a subject name to get a certificate on snow leopard? I found the attribute "kSecMatchCaseInsensitive" which works with key "kSecClassCertificate" in the API "SecItemCopyMatching", but the key kSecClassCertificate is only available for 10.7 and later.
https://developer.apple.com/library/mac/#documentation/Security/Reference/keycha inservices/Reference/reference.html#//apple_ref/doc/uid/TP30000898-CH4g-SW7
Any help is highly appreciated.
Thanks!

I think there is issue with your logon trigger :
"IF ((USER = 'MyAppUSER') OR(USER = 'MyAppREPORTINGUSER')) THEN"
it should be :
IF UPPER(USER) = 'MYAPPUSER' OR UPPER(USER) = 'MYAPPREPORTINGUSER' THEN
because user name stored in Upper case. Check and try.
HTH
Girish Sharma

Case Insensitive search and "IN" Clause - Open SQL

Similar Messages

Maybe you are looking for