case-sensitive

I am in need of a case insensitive string enumeration type in my XML schema (.xsd) file. I can get case insensitive by doing the following. <xs:simpleType name="setDigitalPointType"> <xs:restriction base="xs:string"> <xs:pattern value="[Oo][Nn]" /> <xs:pattern value="[Oo][Ff][Ff]" /> </xs:restriction> </xs:simpleType> The only problem is that I get no enumeration values. I will not get the nice intellesense when using Visual Studio to write my XML. The following will give me enumerations but it is case sensitive. <xs:simpleType name="setDigitalPointType"> <xs:restriction base="xs:string"> <xs

I have a table, users, in an Oracle 9.2.0.6 database. Two of the fields are varchar - last_name and first_name. When rows are inserted into this table, the first name and last name fields are supposed to be in all upper case, but somehow some values in these two fields are mixed case. I want to run a query that will show me all of the rows in the table that have first or last names with lowercase characters in it. I searched the net and found REGEXP_LIKE, but that must be for newer versions of oracle - it doesn't seem to work for me. Another thing I tried was to translate "abcde...z" to "$$$$$

How can I sort a table with a column of varchar2 with characters in varying cases ( UPPER and lower )? For example, when I do an order by of the Name column, I get the following results: ANNIE BOB Daniel annie bob What I want is something like this: ANNIE annie BOB bob Daniel Use lower(field) , e.g. select * from tbl order by lower(name) If you need to address special characters for non-english languages then the other answers about NLSSORT may be what you need. If you don't I would try and KISS and use lower() as it is very easy to remember and use and be read by others (maintainability).

I'm doing some searching of tags, and some users like "cat" while others like "Cat" Go figure... Anyways, is there a way to force a particular find to be case sensitive? Such as: Tag.find(:some-special-option-here) Any ideas? Stefan Gehrig You can also do a case-sensitive search without changing your column properties. SELECT * FROM mytable WHERE myfield='Value' This query matches: Value value VALUE vAlUe and so on While... SELECT * FROM mytable WHERE BINARY myfield='Value' Matches only: Value You can make all strings case sensitive when you create the table by adding "COLLATE utf8_bin" to the

In all the applications/examples I have already seen(eg. wordpress). The column table names use underline rather than camel case. I'd like to know if there are some technical incompatibility problems or it's a convention? Is it dependent of the system platform(Linux/Windows) or the sql dialect(Mysql, postgreSQL, DB2, Oracle, ...). For example in the following table I have used camel case and I haven't already had any problems/warnings about it! If I should/must refactor my table, why should/must I do it? Is SQL case insensitive about the table/column names? What about the dialects? CREATE

Using this code I am able to compare string values. [elementName isEqualToString: @"Response"] But this compares case-sensitively. Is there a way to compare the string without case sensitivity? There’s a caseInsensitiveCompare: method on NSString , why don’t you read the documentation ? The method returns NSComparisonResult : enum { NSOrderedAscending = -1, NSOrderedSame, NSOrderedDescending }; typedef NSInteger NSComparisonResult; …ah, sorry, just now I realized you are asking for case sensitive equality. (Why don’t I read the question? :-) The default isEqual: or isEqualToString: equality

I want to have case insensitive URLs using Apache's mod_speling module, but this is producing unwanted lists of "multiple options" whilst the Apache documention says When set, this directive limits the action of the spelling correction to lower/upper case changes. Other potential corrections are not performed. I'm testing this on an Apache 2.2.16 Unix fresh install but I'm still running into exact the same problems as submitted in 2008. It's unexpected (and not wanted) behaviour when Apache lists a few "multiple choices" (status code 300) when the checkCaseOnly directive is on! I have this in

I am having difficulty with case sensitivity. Can we turn it off? A1 <- c("a", "A", "a", "a", "A", "A", "a") B1 <- c(rep("a", length(A1))) A1 == B1 # [1] TRUE FALSE TRUE TRUE FALSE FALSE TRUE should be all TRUE There's no way to turn off case sensitivity of == , but coercing both character vectors to uppercase and then testing for equality amounts to the same thing: toupper(A1) [1] "A" "A" "A" "A" "A" "A" "A" toupper(A1)==toupper(B1) # [1] TRUE TRUE TRUE TRUE TRUE TRUE TRUE Joris Meys As Josh O'Brien said. To extend a bit on caseless matching in R, that is actually possible with regular