case-sensitive

How to get case-sensitivity in Section names?

笑着哭i 提交于 2019-12-24 02:23:14
问题 I've got an win32 app accessed by users via RDP acess. Each user has his/her own user_app.ini file. When I upgrade my app on the RDP server, I sometimes need to create/modify entries in the user_app.ini file of each user. I wrote a Python script to handle the job that use some upgrade.ini file to update all the user_app.ini files, using the ConfigParser module. My problem is that my section names should be seen as case insensitive, but ConfigParser is case-sensitive regarding sections (while

SQL Server connection string keywords act as case sensitive although they shouldn't be

≯℡__Kan透↙ 提交于 2019-12-23 15:12:53
问题 I use .NET's OdbcConnectionStringBuilder to update a connection string read from a config file, which makes its keys lower case, as documented by MS ("Data Source" -> "data source"). The connection string is used to access MS SQL Server (2008, if it makes a difference). It works fine on my machine (Windows 7 32 bit), and according to MS's documentation it should work: Keywords are not case sensitive However, on several other machines (at least some are 64 bit), the connection to DB could not

HtmlAgilityPack XPath case ignoring

余生颓废 提交于 2019-12-23 09:18:19
问题 When I use SelectSingleNode("//meta[@name='keywords']") it doesn't work, but when I use the same case that used in original document it works good: SelectSingleNode("//meta[@name='Keywords']") So the question is how can I set case ignoring? 回答1: If you need a more comprehensive solution, you can write an extension function for the XPath processor which will perform a case insensitive comparison. It is quite a bit of code, but you only write it once. After implementing the extension you can

How to get case-insensitive elements in XML

若如初见. 提交于 2019-12-23 07:57:47
问题 As far as I know XML element type names as well as attribute names are case sensitive. Is there a way or any trick to get case insensitive elements? Clarification : A grammar has been defined via XSD which is used for some clients to upload data. The users -the content generators- are creating XML files using different tools but many of them are using plain text editors or whatever. Sometimes when this people are trying to upload their files they get incompatibility errors. It is a common

Case sensitive Directory.Exists / File.Exists

梦想与她 提交于 2019-12-23 07:16:16
问题 Is there a way to have a case sensitive Directory.Exists / File.Exists since Directory.Exists(folderPath) and Directory.Exists(folderPath.ToLower()) both return true ? Most of the time it doesn't matter but I'm using a macro which seems not to work if the path doesn't match cases 100%. 回答1: Since Directory.Exists uses FindFirstFile which is not case-sensitive, no. But you can PInvoke FindFirstFileEx with an additionalFlags parameter set to FIND_FIRST_EX_CASE_SENSITIVE 回答2: Based on the

How to equal two strings case sensitively in Linq to SQL?

和自甴很熟 提交于 2019-12-23 04:24:20
问题 How to equal two strings case sensitively in Linq to SQL (in a where query)? Thanks. 回答1: You cannot do it solely within LINQ to SQL. From the documentation: Unsupported System.String Methods in General Queries do not account for SQL Server collations that might be in effect on the server, and therefore will provide culture-sensitive, case-insensitive comparisons by default. This behavior differs from the default, case-sensitive semantics of the .NET Framework. The way to do it is in your own

GitHub Branches: Case-Sensitivity Issue?

耗尽温柔 提交于 2019-12-22 18:37:14
问题 I seem to be having an issue with a repository continually recreating branches locally because of some branches on remote. I'm on a Windows machine, so I suspect that it's a case sensitivity issue. Here's an example couple commands: $ git pull From https://github.com/{my-repo} * [new branch] Abc -> origin/Abc * [new branch] Def -> origin/Def Already up to date. $ git pull -p From https://github.com/{my-repo} - [deleted] (none) -> origin/abc - [deleted] (none) -> origin/def * [new branch] Abc

Case sensitive UriMapper issue in Silverlight 3

…衆ロ難τιáo~ 提交于 2019-12-22 14:41:43
问题 In Navigation API of Silverlight 3 the UriMapper class is case sensitive. For the following uri mapping <nav:Frame Source="/Home"> <nav:Frame.UriMapper> <uriMapper:UriMapper> <uriMapper:UriMapping Uri="" MappedUri="/Views/HomePage.xaml"/> <uriMapper:UriMapping Uri="/entity/{code}" MappedUri="/Views/EntityEditorPage.xaml?code={code}"/> <uriMapper:UriMapping Uri="/{pageName}" MappedUri="/Views/{pageName}Page.xaml"/> </uriMapper:UriMapper> </nav:Frame.UriMapper> </nav:Frame> the "/entity/123" is

Case sensitive UriMapper issue in Silverlight 3

可紊 提交于 2019-12-22 14:41:01
问题 In Navigation API of Silverlight 3 the UriMapper class is case sensitive. For the following uri mapping <nav:Frame Source="/Home"> <nav:Frame.UriMapper> <uriMapper:UriMapper> <uriMapper:UriMapping Uri="" MappedUri="/Views/HomePage.xaml"/> <uriMapper:UriMapping Uri="/entity/{code}" MappedUri="/Views/EntityEditorPage.xaml?code={code}"/> <uriMapper:UriMapping Uri="/{pageName}" MappedUri="/Views/{pageName}Page.xaml"/> </uriMapper:UriMapper> </nav:Frame.UriMapper> </nav:Frame> the "/entity/123" is

R - Recoding column with multiple text values associated with one code

自作多情 提交于 2019-12-22 14:05:28
问题 I'm trying to recode a column to determine the shift of an employee. The data is messy and the word I am looking for must be extracted from the text. I've been trying various routes with if statements, stringr and dplyr packages, but can't figure out how to get them to work together. I have this line of code, but str_match doesn't produce a true/false value. Data$Shift <- if(str_match(Data$Unit, regex(first, ignore_case = TRUE))) { print("First Shift") } else { print("Lame") } recode is