Case Insensitive filter Feature in InputListOfValues Popup

Dear all,
I had taken reference in HRSystem (the tutorial provided by Oracle) ,
[http://st-curriculum.oracle.com/obe/jdev/obe11jdev/ps1/ria_application/developriaapplication_long.htm]
In section "Create a Page Flow" Step 19 popup
You CAN "Search for Jobs whose jobTitle begins with A%. " but
CANNOT "Search for Jobs whose jobTitle begins with a%. " (Lower case of A, no result returns)
As we can filter the column with case insensitive by setting the filterfeature="caseInsensitive" in af:column
I want to use this feature in this InputListOfValues popup.
Anyone has ideas on that?
Million Thanks!
Luis

Can anyone can give me suggestions?
Thanks!

Similar Messages

Mapping with case insensitivity in Filter operator expression

I need to import data from an ODS into DW table.
How can I set this before a certain mapping is run to make it case insensitive?
execute immediate 'alter session set NLS_SORT=BINARY_CI';
execute immediate 'alter session set NLS_COMP=LINGUISTIC';
Thanks,
JGP

Hi,
Use upper(column) in the filter expression.
Regards
Bharath

Case Insensitive Search for the Dashboard Prompt Filter

Hi,
Can anyone help me, how to make dashboard propmt filter to be case insensitive, as of now dashboard propmts are case sensitive by default. How can we achieve this? Any help on this will be appreciated. TIA

I wonder if it can be done. don't know if there's any work-around for it.
Generally, the data that is imported into the SOD system is case sensitive hence the field on which you base your prompt will also be case sensitive.

IOS CLI. How to filter case insensitive?

Hello everyone,
Is there a way to filter IOS output (include/exclude/begin...) case insensitive?
Mario Pinho

Hi Mario,
I see. I don't know any freeware software for such configuration compliance tasks.
If you want to have some kind of automation you could
Download your running-configs to a TFTP server and use grep or a more advanced script to extract the lines your're looking for (the TFTP download could also be done by that scipt =>SNMP)
Use TCL if your devices support it
A simple example:
R1#show int loop0 descriptionInterface Status Protocol DescriptionLo0 up up TESTR1#tclshR1(tcl)#puts [regexp {test} [exec "show int loop0 descr"]]0R1(tcl)#puts [regexp -nocase {test} [exec "show int loop0 descr"]]1R1(tcl)#tclquit
There's a section for EEM scripting, so if you want to create a custom command for your needs, you'll get help there.
Best regards
Rolf

Filter case insensitive

Hi Experts,
Can the filter on table be case insensitive ?
Jdev 11.1.1.4 version
thnks

Hi,
see "filterFeatures" in
http://download.oracle.com/docs/cd/E21764_01/apirefs.1111/e12419/tagdoc/af_column.html
Frank

Is there a way to make the "Find" feature case insensitive?

Is there a way to make the "Find" feature case insensitive?

''Is there a way to make the "Find" feature case insensitive?''
Find ("Ctrl+F")
:uncheck "Match case" on the Find bar
An extension that enhances the Find bar for something they have not added is
*Find All :: Add-ons for Firefox
*:https://addons.mozilla.org/en-US/firefox/addon/find-all/
And if you want a serious fixup for Find see/vote [https://bugzilla.mozilla.org/show_bug.cgi?id=171237 Bug 171237] even though it still misses the point, it should be "exactly" like Opera.

Case insensitive in-memory search

I'm trying to create a case-insensitive in-memory search on a ViewObject. I'm using the following code for performing an in-memory search (~ filtering already retrieved rows from the ViewObject which is based on a webservice)
ViewObject vo = service.getMyViewObject();
vo.setQueryMode(ViewObject.QUERY_MODE_SCAN_VIEW_ROWS);
ViewCriteria vc = vo.createViewCriteria();
vc.setCriteriaMode(ViewCriteria.CRITERIA_MODE_CACHE);
ViewCriteriaRow vcr = vc.createViewCriteriaRow();
vcr.setAttribute("MyAttribute", "like 'abc%' ");
vc.add(vcr);
vo.applyViewCriteria(vc);
vo.executeQuery();This all works well .. but when I add vcr.setUpperColumns(true); and change line vcr.setAttribute("MyAttribute", "like 'abc%' "); into vcr.setAttribute("MyAttribute", "like 'ABC%' ");I get the following exception :
Caused by: oracle.jbo.expr.JIException: Method call has no object context
     at oracle.jbo.expr.JIParserMethodNode.evaluate(JIParserMethodNode.java:71)
     at oracle.jbo.expr.JIParserNode.evaluate(JIParserNode.java:740)
     at oracle.jbo.RowMatch.rowQualifies(RowMatch.java:230)
     at oracle.jbo.server.ViewObjectImpl.rowQualifies(ViewObjectImpl.java:1387)
     at oracle.jbo.server.QueryCollection.rowQualifies(QueryCollection.java:2308)
     at oracle.jbo.server.QueryCollection.removeUnqualifiedRows(QueryCollection.java:549)
     at oracle.jbo.server.QueryCollection.buildResultSet(QueryCollection.java:719)
     at oracle.jbo.server.QueryCollection.executeQuery(QueryCollection.java:666)
     at oracle.jbo.server.ViewObjectImpl.executeQueryForCollection(ViewObjectImpl.java:3655)So, my question is: is it possible to do a case-insensitive in-memory search or should I convince my customer to drop the feature-request ;-)

Maybe I should add some extra info:
The viewobject is based on a webservice and not a database. I do not have access to the implementation of that webservice ( I only consume its data and store the results in the viewobject's datacollection ). The VO has no query attached and only has transient attributes. Therefore, I cannot use vo.setWhereClause() ~ I think.
Once I filled the viewobject's datacollection ( by overriding executeQueryForCollection() and createRowFromResultSet(...) ), I would like to filter the datacollection with filterparameters (from my jsf page). This can be enabled by first calling vo.setQueryMode(ViewObject.QUERY_MODE_SCAN_VIEW_ROWS) an
The in-memory search facility in the ViewObject's implementation seems to be restricted in filtering the viewobject's datacollection.
I've tried using ViewCriteria and RowMatch to filter the data ... with no success.
I hope I have explained my situation a bit more. Perhaps someone can help me out ?

How do I move my large iTunes collection from a case-sensitive hard drive to a case-insensitive hard drive?

I currently keep my iTunes media on an external hard drive because it takes up too much space on my machine. I recently discovered that it was formatted as case-sensitive when I bought it, and now months later I'm having issues. When attempting to back up my files on a case-insensitive hard drive, the operation failed due to conflicting file/folder names (Artist and artist are now considered the same file name and one would have to overwrite the other). I now have a large iTunes file collection that is stuck on the case-sensitive hard drive, and I want to save a backup on a case-insensitive drive.
Is there a way to identify all cases where multiple files/folders have the same title/album/artist but different spelling so there will be no conflicts? The folder/file names would have to be crossed referenced to highlight any cases where File/fiLe/file would cause a problem.
I imagine there is a way to do this using iTunes script or Automator or a command in terminal or something rather than going through and checking/fixing all the information for thousands of songs by hand. I'm at the limits of my minimal development skills, so any help would be appreciated.

You should be able to use either "Carbon Copy Cloner" or "SuperDuper" (free for this purpose) to copy your case-sensitive volume to an empty case-insensitive one. Make at least two such copies on different drives. One is not enough to be safe.
If there are any name conflicts—that is, files in the same folder with names that differ only in case, such as "File" and "file"—then you will either get an error or one of the files won't be copied. You must ensure either that no such conflicts exist, or that the consequences are not important. How you do that is up to you. Unless you went out of your way to create conflicts, they probably don't exist.
Then erase the source volume in Disk Utility as case-insensitive. This action will remove all data from the volume.
Restore from one of your backups using the same application you used to create it, or use the "Restore" feature of Disk Utility, which will be faster. Search its built-in help for the term "duplicate" if you need instructions.

Case-insensitive -- what's a scriptor to do?

Here's my delima: (from a tcsh)
% ls
file1.txt file2.TXT file3.txt
% ls file{1,2,3}.TXT
file1.TXT file2.TXT file3.TXT
% ls *.TXT
file2.TXT
% rm *.txt
I've written hundreds of unix (csh,tcsh, perl) scripts since around 1988. I never considered that some day UNIX would ignore case in filenames.
As you can imagine, I'm going to have to re-write dozens of scripts, now that I have this case-insensitive "feature".
QUESTION 1: Is there some way to turn off the ignore-case in Apple unix? What are the consequences of such a bold act?
QUESTION 2: Is there a simple variable, switch, or something, that tells the shell (tcsh) that files are case-sensitive (e.g. *.TXT would match *.txt)? Same request goes for telling filec that is should ignore case.
PowerBook G4 Mac OS X (10.3.9)

Hi Bill,
   I see what you're saying. When the shell passes information to the filesystem, case ceases to matter. However, C Webber is talking about the reverse situation. HFS+ is case-insensitive but it is case-preserving. Whatever case is used in the naming of a file is reproduced faithfully in read operations and shells are by default case-sensitive. C Webber's example was filename globbing. The shell reads the names of the files and looks for matches in a case-sensitive fashion. In that case, case will matter.
   I can see where this would cause problems. You might test for the existence of a file in a case-sensitive fashion, find out that it doesn't, write to the filesystem and blow away a file even though you were careful. You know that something like that happened with the Perl install script, causing it to blow away dozens of its own man pages.
C. Webber,
   I did a search of the tcsh man page and found nothing suggesting that you can turn off case-sensitivity in globbing. You can do so in completion but it appears that rewrites will be necessary. I encourage you to view this as an opportunity and switch to a more powerful shell. I agree with you that this issue is unique to Mac OS X but every flavor of UNIX has its own issues. We've all had to make changes to migrate scripts. I've certainly had to do that to migrate some of my scripts to Linux and some won't migrate at all. (I use AppleScript in many of my scripts)
Gary
~~~~
   "The glory of creation is in its infinite diversity."
   "And in the way our differences combine to create meaning and beauty."
         -- Dr. Miranda Jones and Spock, "Is There in Truth No Beauty?",
            stardate 5630.8

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') )

Conversion from a case-sensitive to case-insensitive disk configuration.

Being an old Unix user, I configured my disks to be case-sensitive. I've discovered that patches and updates to some applications fail due to changes in the case used for file names.
Is there a painless way to convert a case-sensitive file system to one that is case-insensitive?

I don't have current version of SoftRAID 4.0 but I thought that was one of its features, just as it can change the block size for arrays from 16-32-64-128k etc on the fly.
I haven't used it, but iPartition claims to be able to convert in-place between case-sentitive and case-insensitive HFS+ formats.
The trouble is, even then, a restore may not work properly.
http://www.dslreports.com/forum/r19614460-Convert-hard-drive-to-HFS-that-is-not- case-sensitive

Custom tag attribute case insensitive??

We ran in to an interesting "feature" of custom tags: The attributes in the
          tags seem to be case insensitive.
          For example, if you play with the "tagext/quote" example provided with the
          WebLogic server installation, you can change the line in showcode.jsp to be
          like:
          <quote:code quoteColor="blue" COMMENTCOLOR="purple"
          defaultFont="face=Helvetica color=gray">
          and the generated java servlet code will still call the "setCommentColor()"
          method in the CodeTag class. Almost like it searches for a matching
          "attribute" in the .tld file and uses it. If you put multiple entries in
          the .tld file for different cases, it still picks the first one it finds and
          ignores the case differences.
          The J2EE/JSP spec indicates that custom tags are case sensitive, I assumed
          that is supposed to include their attributes.
          It bit us because we want to have attributes which differ by case only
          (don't ask).
          -Greg
          Check out my WebLogic 6.1 Workbook for O'Reilly EJB Third Edition
          www.oreilly.com/catalog/entjbeans3 or www.titan-books.com


I had the same problem in a design a couple of months ago and could not get around it so I switched the functionality into code and out of the tag lib.
I take it you are trying to do something like this?
<%
String value="hiworld";
%>
<mytaglib:saysomething value="<%=value%>"/>

Make LR filters case insensitive?

Is there any way to make LR Text filters case insensitive? I can't imagine why anyone would want a filter to be case sensitive. Thanks.

When I tried filtering on keywords the filter is case sensitive. For example, if I define a text filter for "Fall Color" the images are found but if I change the filter to "fall color" no images are found. I would like the filter to return the same images for either string? Is there a way to configure LR to do this?

Possible bug in renaming files - case insensitive

I tried to rename a file from "TestVoToNameValuePairs" to
"TestVOToNameValuePairs" and FB 2.2.1b gave me the following error:
Trying to use an unsupported feature
svn: Cannot move path
'V:\Flex2\Attune_04\tests\utils\TestVoToNameValuePairs.as' into
itself
Bug? Or am I missing something? Looks like the name check is
case-insensitive by accident.
S.

The "svn" in this error message indicates that Subversion is
doing the complaining. I believe that Subversion is
case-insensitive, at least on Windows. This FAQ might be helpful:
http://subversion.tigris.org/faq.html#case-change
- Peter

How do I make Merge operation into the target table case insensitive?

Hi All,
We have a target table that has a varchar 2 column called nat_key and a map that copies over data from a source table into the target table.
Based on wheteher the values in the nat_key column matches between the source and the target, an update or an insert has to be done into the target table.
Let us say target table T has the following row
nat_key
EQUIPMENT
Now, my source table has the same in a different case
nat_key
equipment
I want these rows to be merged .
In the OWB map, I have given the property of nat_key column in the target table as 'Match while updating' = 'Yes'. Is there a built in feature in OWB, using which I can make this match as case insensitive?
Basically, I want to make OWB generate my mapping code as
if UPPER(target. nat_key)=upper(source.nat_key) then update...else insert.
Note: There is a workaround with 'Alter Session set nls_sort=binary_ci and nls_comp=linguistic', but this involves calling a pre-mapping operator to set these session parameters.
Could anyone tell me if there is a simpler way?

Hi,
use an expression operator to get nat_key in upper case. Then use this value for the MERGE. Then nat_key will only be stored in upper case in your target table.
If you have historic data in the target table you have to update nat_key to upper case. This has to be done only once and is not necessary if you start with an empty target table.
Regards,
Carsten.

Case Insensitive filter Feature in InputListOfValues Popup

Similar Messages

Maybe you are looking for