Treeset.contains(String) is case sensitive ?

hi
i noticed that treeset.contains(String) is case sensitive.
when you all are testing keywords do you therefore put everything to lower case to test ?
just double checking something extremely simple

Well strings are case sensitive. Try using String.equalsIgnoreCase(String) to compare strings without regards to case. As for using it in collections, you may want to convert all strings to upper or lower case before placing them into collections (this may not always be possible due to "business reasons").
Note: contains(String) on the Collection interface uses Object.equals(Object o) to test object equality. The implentation of equals on String will return true if and only if the argument is not null and is a String object that represents the same sequence of characters as this object. Case will not be ignored in this implementation.
Hope this helps.

Similar Messages

How to make a String not case sensitive

Hi,
In my application, I test
[ if (record.startsWith(remark)) ]
The value of [remark] is a fiexd word (e.g. "Hello").
But I would the test passed for all other words which have the same letters as it sucu as "HELLO", "HELlo" ...
Do you have any good idea?
Thx.
Pengyou

use
if(record.toLowerCase.startsWith("hello")) ..

Still need help with case sensitive strings

Hello guy! Sorry to trouble you with the same problem again,
but i still need help!
"I am trying to create a scrypt that will compare a String
with an editable text that the user should type to match that
String. I was able to do that, but the problem is that is not case
sensitive, even with the adobe help telling me that strings are
case sensitive. Do you guys know how to make that comparison match
only if all the field has the right upper and lower case letters?
on exitframe
if field "t:texto1" = "Residencial Serra Verde"then
go to next
end if
end
|----> thats the one Im using!"
There were 2 replys but both of them didnt work, and the
second one even made the director crash, corrupting even previously
files that had nothing to do with the initial problem..
first solution given --
If you put each item that you are comparing into a list, it
magically
makes it case sensitive. Just put list brackets around each
item.
on exitframe
if [field "t:texto1"] = ["Residencial Serra Verde"] then
go to next
end if
end
Second solution given--
The = operator is not case-sensitive when used on strings,
but the < and > operators are case-sensitive.
So another way to do this is to check if the string is
neither greater than nor less than the target string:
vExpected = "Residencial Serra Verde"
vInput = field "t:texto 1"
if vExpected < vInput then
-- ignore
else if vExpected > vInput then
-- ignore
else
-- vExpected is a case-sensitive match for vInput
go next
end if
So any new solutions??
Thanks in advance!!
joao rsm

The first solution does in fact work and is probably the most
efficient way
of doing it. You can verify that it works by starting with a
new director
movie and adding a field named "t:texto1" into the cast with
the text
"Residencial Serra Verde" in the field. Next type the
following command in
the message window and press Enter
put [field "t:texto1"] = ["Residencial Serra Verde"]
You will see it return 1 which means True. Next, make the R
in the field
lower case and execute the command in the message window, it
will return 0
(true).
Now that you know this works, you need to dig deeper in your
code to find
what the problem is. Any more info you can supply?

Case sensitivity in Oracle Text

I am familiar with the mixed_case parameter, and in my setup it is set to no, so all searches are case-insensitive. This is what I want 95% of the time, but is there a way to specify (at a query level) that a contains search is case sensitive?

Hi,
Would be nice, but the tokens are converted to uppercase on indexing. For example:
SQL> create table test (col1 varchar2(20));
Table created.
SQL> insert into test values ('MixEd cAsE');
1 row created.
SQL> create index test_idx on test(col1)
2 indextype is ctxsys.context;
Index created.
SQL> select token_text from dr$test_idx$i;
TOKEN_TEXT
CASE
MIXED
So, since they are actually stored/converted to uppercase there is nothing case-sensitive for your query to compare to.
On the flip side, if you index case-sensitive, the tokens are stored mixed-case.
SQL> drop index test_idx force;
Index dropped.
SQL> begin
2 ctx_ddl.create_preference('mylex', 'BASIC_LEXER');
3 ctx_ddl.set_attribute('mylex', 'mixed_case', 'yes');
4 end;
5 /
PL/SQL procedure successfully completed.
SQL> create index test_idx on test(col1)
2 indextype is ctxsys.context
3 parameters('lexer mylex');
Index created.
SQL> select token_text from dr$test_idx$i;
TOKEN_TEXT
MixEd
cAsE
Now you can do something with your query to make it do what you want. You'd have to check performance to see if it is worth it.
Ron

Case sensitive string variable?

Hello,
I use the following code to determine whether I am opening a DAT file or a TDM file. Some of it is complicated by a bug in 2010 but that is not relevent for this particular problem. Up until today it has worked perfectly, probably because the TDM files I have been opening were written using code from the same autosequence. Today I was opening files saved by DIAdem using the standard save as toolbar button.
T2 = NameSplit(T1,"E") ' extract file extension
if T2 <> "TDM" then 'case sensitive??
CallDataLoadHdFile(T1) 'Temporary fix from NI until DataFileLoadSel problem is fixed
CallDataLoadSel(DATADRVUSER&T1, ChList_, 0) 'Temporary fix from NI until DataFileLoadSel problem is fixed
' Call DataFileLoadSel(DATADRVUSER&T1,T2,"[1]/["&ChList_&"]","") ' Load selected data channels from next file 'Commented out by SA 8/6/11, as it doesn't work in 2010
else
CallDataFileLoadSel(DATADRVUSER&T1,T2,"[1]/["&ChList_&"]","") ' Load selected data channels from next file
endif
The code failed because the file I was opening had the extension tdm, and thus the value of T2 was "tdm". I couldn't believe it but I wondered whether the if...then loop was case sensitive to the value of T2. It was... When I changed the second line of code as follows (i.e. lower case tdm) it worked.
if T2 <> "tdm" then'case sensitive??
It seems that when DIAdem saves files it applies a lower case extension but my code has applied uppercase letters. For reasons of backwards compatability I can't really change my code to save with lower cases.
I've tried using:
if T2 <> "TDM" or "tdm" then'case sensitive??
but that doesn't work.
So, my question is: how do I correct the 'or' statement so that it works, or is there a function I can use to make the if...then loop and/or T2 case insensitive?
Thanks.

Try InStr for comparing instead:
T2 = "TDM"
If InStr(1, T2, "tdm", vbTextCompare) <> 0 then
MsgBox "Found TDM"
end if
(T2 contains capital TDM whereas Instr used lowercase tdm for comparison....)

Case Sensitive String

Hi,
I need to read an argument but without case sensitivity, so far I have:
if (args[2].equals("MEAN"))
How can I make this line case insensitive?
Thank you
Mike

Hi,
I need to read an argument but without case
sensitivity, so far I have:
if (args[2].equalsIgnoreCase("MEAN"))
How can I make this line case insensitive?
Thank you
Mike

How to make PowerPivot case sensitive?

Hi all,
I just discovered that PowerPivot is case-insensitive, which is quite a big problem for me. The only discussion of this I found so far is here: http://dennyglee.com/2010/06/18/powerpivot-you-are-so-insensitive-case-that-is/ .
That didn't fully answer my question though, is it possible to change this behaviour and make it case sensitive?
The reason it's a problem for me is that I have a column (from external data source) used as an ID in a relationship, which contains a string of random characters. If it so happens that two entries have an ID which only differs by a case of a letter, everything
blows up. More precisely, I can no longer import the data into the table where the column is used as a PK, because it is not unique.
Thanks for any comments,
Jurgis

You can post bugs on Connect.
Thanks!
Ed Price, SQL Server Customer Program Manager (Blog,
Small Basic,
Wiki Ninjas,
Wiki)
Answer an interesting question?
Create a wiki article about it!

Sort column by without case sensitive using Comparator interface

Hello,
When i sorted my values of a column in a table it was showing all sorted upper case letters at top rows and all sorted lower case letters on bottom. So i would like to sort values without case sensitive order. Like. A, a, B, b, C, c....
I am using Collection class to sort vector that contains the values of a column as an object and using Comparator interface to sort the values of a column in either ascending and descending order. It facilitates to compare two objects like.
<class> Collections.sort(<Vector contains values of column to be sort>, <Comparator interface>);
and in interface it compares two objects ((Comparable) object).compareTo(object);
Now Let's suppose i have three values say Z, A, a to sort then this interface sorted in ascending order like A, Z, a
but the accepted was A, a, Z. So how can i get this sequence. I would like to sort the values of a column without case sensitive manner.
Thanks
Ashish Pancholi
Edited by: A.Pancholi on Dec 29, 2008 1:36 PM

[http://java.sun.com/javase/6/docs/api/java/lang/String.html#CASE_INSENSITIVE_ORDER]

Case sensitive field in to_date function

update "Ab_Order" set "OrderDate" = to_date("Order Date String", 'yyyy/mm/dd)
Here the OrderDate column is of type Date
"Order Date String" is varchar2. Iam trying to copy the data from "Order Date String" which contains data in this format '2011/04/24' to OrderDate column to perform some date functions
when I try to run this query it gives a error: ORA-01830: date format picture ends before converting entire input string
So I tried to run this query by creating a test table wit 2 columns : update testtable set column1 = to_date(field1, 'yyyy/mm/dd')
where column1 is date field and field1 is varchar2 and this worked.
So Iam assuming this is the problem with case sensitive fieldnames . As far as i know we should include case sensitive fields in double quotes. Is there anything else to do wit the to_Date function. Can anyone please let me know how to do that.

Hi,
Welcome the the forum!
882431 wrote:
update "Ab_Order" set "OrderDate" = to_date("Order Date String", 'yyyy/mm/dd)It looks like you're missing a single-quote right before the last ')'.
Here the OrderDate column is of type Date
"Order Date String" is varchar2. Iam trying to copy the data from "Order Date String" which contains data in this format '2011/04/24' to OrderDate column to perform some date functions
when I try to run this query it gives a error: ORA-01830: date format picture ends before converting entire input stringThat error occurs when when you have characters in the 1st argument that do not correspond to anything in the 2nd argument. For example:
TO_DATE ( '30-Aug-2011 12:00'
, 'dd-Mon-yyyy'
)In this example, TO_DATE doesn;t know what to do with the ' 12:00' at the end of the 1st argument. According to the 2nd arguemnt, there's only supposed to be 11 characters in the string. So it raises the ORA-01830 error.
So I tried to run this query by creating a test table wit 2 columns : update testtable set column1 = to_date(field1, 'yyyy/mm/dd')
where column1 is date field and field1 is varchar2 and this worked.
So Iam assuming this is the problem with case sensitive fieldnames . As far as i know we should include case sensitive fields in double quotes. Is there anything else to do wit the to_Date function. Can anyone please let me know how to do that.Case sensitive column names are a bad idea because they cause so amny problems, but I don't think this is one of those problems. It's more likely that you need to use SUBSTR (or some other string manipulation function) on "Order Date String" before using it in TO_DATE.
Whenever you have a problem, please post a little sample data (CREATE TABLE and INSERT statements, relevant columns only) from all tables, so people can re-create the problem and test their ideas.
Also post the results you want from that data, and an explanation of how you get those results from that data, with specific examples.
Always say which version of Oracle you're using.

Case Sensitive problem in Select Option for wild card search

Hi,
Can anyone please let me know how to make the wild card search in any select-option non case-sensitive. What I mean by this is for eg. we want to find out all the POs with short text containing the word 'process', what we do we populate a range with OPTION = 'CP' and LOW = 'process' and select EKPO with short text in this range. This select is however case-sensitive and POs with short text containing 'Process' is not retrieved. But my requirement is that this should be non case-sensitive and both the POs should be in the result set.

Hi,
Hope this helps you
CS:
You can select characters in operand2 for a direct comparison by adding the escape symbol "#" before the required characters. For these characters, upper/lower case is taken into account, wildcard characters and the escape symbol itself do not receive special treatment, and trailing blanks in operands of type c are not cut off.
Covers Pattern: True, if the content of operand1 fits the pattern in operand2. Wildcard characters can be used for forming the operand pattern, where "" represents any character string, and "+" represents any character. Upper/lower case is not taken into account. If the comparison is true, sy-fdpos contains the offset of operand2 in operand1, whereby leading wildcard characters "" in operand2 are ignored if operand2 also contains other characters. If the comparison is false, sy-fdpos contains the length of operand1.
Regards
Krishna

CSS cookieurl: case sensitive?

Hello,
As far as I understand, the HTTP header cookie field, and the embedded cookie (in a URL) are case-sensitive. Is this correct?
The settings look like this:
content stickyCookie
advanced-balance cookieurl
string prefix "SESSION_ID="
On the HTTP header the cookie field looks like this:
Set Cookie: SESSION_ID=ABCDEF
But if instead of this, the request comes from a client with the cookie embedded in the url, it looks like this:
http://localhost/Info/index;session_id=ABCDEF?page=home.
Is this field case-sensitive for the CSS? I know it is for the ACE, as I have done this and there is the "cookie secondary" command where you can specify how the url-embedded cookie looks like.
So I am afraid there is no way of making this work on a CSS?
Any help will be much appreciated!

Hi Javier,
The Cisco CSS is case-sensitive when searching for this string.
When configuring the CSS 11000 and 11500, determine first if you need a server cookie string. If the string operation under the content rule is match-service-cookie, which is the default setting, this parameter must be configured. In this case the service cookie string is matched against the cookie contained in the HTTP header for load balancing decision.
If the string operation under the content rule is set to the hash method, this parameter is not needed. In order to select one of the available servers, the cookie contained in the HTTP header is mathematically processed using a hashing algorithm. If available, the hash algorithm assigna the connection carrying a certain cookie to the same server. This example focuses on the match-service-cookie case.
Note: Cookies are case sensitive.
Configuring the Service
training4(config># service server_g
training4(config-service[server_g])# string LV2KJK (the server cookie text)
training4(config># service server_h
training4(config-service[server_h])# string AARIKA
Configuring the Content Rule
Note: Cookies require a Layer 5 rule.
You can create a Layer 5 rule by adding a URL.
For example, .
A Layer 4 rule can be promoted to a Layer 5 rule by issuing the advanced-balance cookies command.
Choose the advanced-balance method.
training4(config-owner-content[cookie-layer5])# advanced-balance cookies
Configure the string operation.
training4(config-owner-content[cookie-layer5])# string operation ?
match-service-cookie (DEFAULT)
hash-crc32
hash-xor
hash-a
Define the starting/ending bytes.
training4(config-owner-content[cookie-layer5])# string range 1 to 200
Start byte position of cookie/url after header (Range:1-600)
Specify the prefix located in the string range.
training4(config-owner-content[cookie-layer5])# string prefix "ASPSESSION"
"Quoted textual information"(Len: 0-32)
Indicate how many bytes to skip after the starting prefix.
training4(config-owner-content[cookie-layer5])# string skip-length 9
"Quoted textual information"(Len: 0-32)
Indicate how many bytes after the prefix/skip-length make-up the string.
training4(config-owner-content[cookie-layer5])# string process-length 6
Integer value(Range: 0-64)
If no string process length is configured, search after end of string character.
training4(config-owner-content[cookie-layer5])# string eos-char "&"
"Quoted textual information"(Len: 0-5)
Specify the failover in the event that a server goes down or is suspended.
training4(config-owner-content[cookie-layer5])# sticky-serverdown-failoversticky-srcip
sticky-srcip-dstport
sticky-srcip
balance (Default)
redirect
reject
Below is an example of a cookie string, and how some of the parameters work.
ASPSESSIONJJKKJJKK=LV2KJK44444444
!--- The string prefix = ASPSESSION.
!--- The string skip-length = 9. Skip
!--- nine characters after the prefix.
!--- The string process-length = 6, which would make
!--- the string LV2KJK matching service server_g.
ASPSESSIONSQPMMJHK=AARIKAMDESLD
!--- Matches service server_h.
Below is a sample configuration for the cookie strings.
!************************** SERVICE **************************
service server_g
ip address 172.17.63.240
string LV2KJK
active
service server_h
ip address 172.17.63.241
string AARIKA
active
!*************************** OWNER ***************************
owner braden
content server-cookie
protocol tcp
vip address 172.17.63.199
port 80
advanced-balance cookies
string range 1 to 200
string prefix "ASPSESSION"
string skip-length 9
string process-length 6
add service server_g
add service server_h
active
Kindly tell if this information is of any use to you.
Sachin garg

Case sensitive problem in

Hi Experts !

Hi Experts!
I have used EVS in table column. When I click that particular column, it shows pop window correctly.
It contains the data like that in pop window.
"A" -
> Apple
"B" -
> Ball
"C" -
> Cat
My problem is when I enter the value directly into that column instead of selecting value from pop up window , I face case sensitive problem. For example if I enter
"a" instead of "A" i got the following error <b>The stringer "a" does not occur in the quantity of the permitted values</b>
How to solve this error?
pl help me.
Advance Thanks.

About lucene's case sensitive

I use lucene to search word "abc" results:
1. abc ...
2.ABC ...
how can I make lucene case sensitive??

Why you don't implement this in Analyzer.
Example:
import org.apache.lucene.analysis.Analyzer;
import org.apache.lucene.analysis.TokenStream;
import org.apache.lucene.analysis.StopFilter;
import org.apache.lucene.analysis.LowerCaseTokenizer;
import org.apache.lucene.analysis.PorterStemFilter;
import java.io.Reader;
import java.util.Hashtable;
* PorterStemAnalyzer processes input
* text by stemming English words to their roots.
* This Analyzer also converts the input to lower case
* and removes stop words. A small set of default stop
* words is defined in the STOP_WORDS
* array, but a caller can specify an alternative set
* of stop words by calling non-default constructor.
public class PorterStemAnalyzer extends Analyzer
    private static Hashtable _stopTable;
     * An array containing some common English words
     * that are usually not useful for searching.
    public static final String[] STOP_WORDS =
        "0", "1", "2", "3", "4", "5", "6", "7", "8",
        "9", "000", "$",
        "about", "after", "all", "also", "an", "and",
        "another", "any", "are", "as", "at", "be",
        "because", "been", "before", "being", "between",
        "both", "but", "by", "came", "can", "come",
        "could", "did", "do", "does", "each", "else",
        "for", "from", "get", "got", "has", "had",
        "he", "have", "her", "here", "him", "himself",
        "his", "how","if", "in", "into", "is", "it",
        "its", "just", "like", "make", "many", "me",
        "might", "more", "most", "much", "must", "my",
        "never", "now", "of", "on", "only", "or",
        "other", "our", "out", "over", "re", "said",
        "same", "see", "should", "since", "so", "some",
        "still", "such", "take", "than", "that", "the",
        "their", "them", "then", "there", "these",
        "they", "this", "those", "through", "to", "too",
        "under", "up", "use", "very", "want", "was",
        "way", "we", "well", "were", "what", "when",
        "where", "which", "while", "who", "will",
        "with", "would", "you", "your",
        "a", "b", "c", "d", "e", "f", "g", "h", "i",
        "j", "k", "l", "m", "n", "o", "p", "q", "r",
        "s", "t", "u", "v", "w", "x", "y", "z"
     * Builds an analyzer.
    public PorterStemAnalyzer()
        this(STOP_WORDS);
     * Builds an analyzer with the given stop words.
     * @param stopWords a String array of stop words
    public PorterStemAnalyzer(String[] stopWords)
        _stopTable = StopFilter.makeStopTable(stopWords);
     * Processes the input by first converting it to
     * lower case, then by eliminating stop words, and
     * finally by performing Porter stemming on it.
     * @param reader the Reader that
     *               provides access to the input text
     * @return an instance of TokenStream
    public final TokenStream tokenStream(Reader reader)
        return new PorterStemFilter(
            new StopFilter(new LowerCaseTokenizer(reader),
                _stopTable));
}

Is a Full Text Index search case sensitive or not in SQL Server 2012?

I setup full text index on my contact table and am attempting to run a search on it using the following query:
SELECT *
FROM sysdba.Contact C
WHERE CONTAINS(C.FirstName, 'Test')
OR CONTAINS(C.LastName, 'Test')
The problem is it's clearly running a case sensitive search. I did a quick search to find out how to change it to be case in-sensitive and found two pages (both for SQL Server 2012) with conflicting answers:
1 - MSDN - "Query with Full-Text Search" - http://msdn.microsoft.com/en-us/library/ms142583(v=sql.110).aspx
Case sensitivity
Full-text search queries are case-insensitive. However, in Japanese, there are multiple phonetic orthographies in which the concept of orthographic normalization is akin to case insensitivity (for example, kana = insensitivity). This type of orthographic normalization
is not supported.
1 - TechNet - "Full-Text Search (SQL Server)" - http://technet.microsoft.com/en-us/library/ms142571(v=sql.110).aspx
Full-text queries are
not case-sensitive. For example, searching for "Aluminum" or "aluminum" returns the same results.
Can someone please explain this? Is it possible to do it without it being case sensitive? If yes, how?
(Sorry, I couldn't make those links b/c TechNet hasn't verified my account)
Thank you for your time and help,
Hanan

Whats the collation setting for the columns? try using a case insensitive collation as below
SELECT *
FROM sysdba.Contact C
WHERE CONTAINS(C.FirstName COLLATE SQL_Latin1_General_CP1_CI_AS, 'Test')
OR CONTAINS(C.LastName COLLATE SQL_Latin1_General_CP1_CI_AS, 'Test')
Please Mark This As Answer if it helps to solve the issue Visakh ---------------------------- http://visakhm.blogspot.com/ https://www.facebook.com/VmBlogs

How to retrieve column names in a query in a case sensitive way

Given a query, I want to extract all the column names/aliases in the query in a case-sensitive way.
When I use dbms_sql.describe_columns() or java.sql.ResultSetMetaData classes getColumnName() or getColumnLabel()
it returns the columns name ONLY in Upper case.
My application needs to extract the column names in the same case as it appears in the query string.
Is there any API to get this without parsing the SQL query string?
Thanks
PS: The dbms_sql.describe_columns() returns the column name in upper case.
declare
IS
l_column_recs DBMS_SQL.DESC_TAB;
l_cur NUMBER;
l_column_count NUMBER;
BEGIN
l_cur := dbms_sql.open_cursor;
dbms_sql.parse(l_cur, 'select target_type from targets', dbms_sql.NATIVE);
dbms_sql.describe_columns(l_cur, l_column_count, l_column_recs);
FOR i IN l_column_recs.FIRST..l_column_recs.LAST
LOOP
dbms_output.put_line(l_column_recs(i).col_name);
end loop;
end;
/

As far as the result set is concerned, though, the column name is in all upper case. If you query the data dictionary, you would see that the TARGET_TYPE column in the TARGETS table is stored in upper case.
The way Oracle works is that column names that are not enclosed in double-quotes are converted to upper case in the data dictionary and elsewhere and then Oracle looks for the column name in the table definition. That is what allows Oracle to have case-insensitive identifiers unless a user specifies case-sensitive identifiers by enclosing the identifier in double quotes.
If you changed the query to be
SELECT target_type as "target_type"
FROM targetsOracle should report the alias in a case sensitive fashion because you've now indicated that the alias should be treated as case sensitive.
Justin

Treeset.contains(String) is case sensitive ?

Similar Messages

Maybe you are looking for