case-sensitive

i'm using regex for filtering some contents. var word = new RegExp(filterWord,"gi");// "gi" means Global and insensitive content = content.replace(word, "");//removes "word" from content This code works properly but when regex get uppercase "İ" it dont replace word. ex: if filterWord = istanbul and content = "İstanbul"; Above code not working properly , if i write istanbul to İstanbul ,it is working but this time it is not insensitive , how can i solve this problem ? How regEx works with Small-Case and Upper-Case chars is based on the Hex-Code of the characters and how they are represented in

In SQL Server (2000 or 2005) is it possible to set the database or server collation so that identifier names (tables, columns, etc) need to be in the correct case? If so, is that true of all case-sensitive collations or is it a separate setting? (I've always thought of case-sensitivity applying to data, not to names of objects). Presumably this would break an application if its stored procs and queries weren't written with consistent case? Is there a way to deal with this without having to ensure all queries use the correct case, such as setting the collation of a database connection? I'm

How should I go about enabling case sensitive request handling if using IIS Express? Is there a setting in IIS Express? or can a URL Rewrite rule accomplish this? or perhaps catch-all HTTP Handler to do the case check? The goal is to be able to catch case inconsistencies locally, with respect to static files, before deployment to both IIS and S3 (where S3 is case sensitive). Thanks IIS is case-sensitive... ...but not for files. It is a misnomer that IIS is case-insensitive, it is the Windows file system that is case-insensitive, not IIS. If a URL contains a file path then IIS asks Windows if

Hi I need to create xml from data in form to send it to webservice. The problem is that .append() is case insensitive, so .append('<EDO />') will create <edo> . But xml is case sensitive, so is there a way how to solve this? And I've chosen to use domObject instead of string, because this way I don't have to write endtags, what would be very difficult in my scenario. Try using $.parseXML() to create the XML element: yourObject.append($.parseXML("<EDO />").documentElement); Finally as @Frédéric Hamidi said, to make case sensitive xml I used these functions: var domA = $.parseXML("<EDO_A />")

Under SQL Server. A table contains some text with different cases. I want to sort them case-sensitive and thought that a COLLATE in the ORDER BY would do it. It doesn't. Why? CREATE TABLE T1 (C1 VARCHAR(20)) INSERT INTO T1 (C1) VALUES ('aaa1'), ('AAB2'), ('aba3') SELECT * FROM T1 ORDER BY C1 COLLATE Latin1_General_CS_AS SELECT * FROM T1 ORDER BY C1 COLLATE Latin1_General_CI_AS Both queries return the same, even if the first one is "CS" for case-sensitive aaa1 AAB2 aba3 (in the first case, I want AAB2, aaa1, aba3 ) My server is a SQL Server Express 2008 (10.0.5500) and its default server

Thanks to the help with my previous homework question Regex to match tags like <A>, <BB>, <CCC> but not <ABC> , but now I have another homework question. I need to match tags like <LOL> , <LOLOLOL> (3 uppercase letters, with repeatable last two letters), but not <lol> (need to be uppercase). Using the technique from the previous homework, I tried <[A-Z]([A-Z][A-Z])\1*> . This works, except there's an additional catch: the repeating part can be in mixed case! So I need to also match <LOLolol> , <LOLOLOlol> , because it's 3 uppercase letters, with repeatable last two letters in mixed case. I

Is hTTp://foo.com the same as Http://foo.COM ? I know that hostnames are not sensitive but path names and query parts are sensitive. Tobu The scheme is case-insensitive: http://tools.ietf.org/html/rfc3986#section-3.1 The hostname is also case-insensitive, since it's DNS. The rest is case sensitive. It is not sensitive in practice but in theory only lower case is allowed. From RFC 1738 2.1. The main parts of URLs A full BNF description of the URL syntax is given in Section 5. In general, URLs are written as follows: <scheme>:<scheme-specific-part> A URL contains the name of the scheme being