Accessing the elements is case-sensitive.
访问元素是区分大小写的。
Some applications are case-sensitive, so be careful!
一些应用程序是区分大小写的，所以要小心！
The password of the hub database user (case-sensitive).
hub数据库用户的密码(区分大小写)。
The case-sensitive name of the schema to be backed up.
要备份的模式的大小写敏感名。
Both the attribute name and item type name are case-sensitive.
属性名和条目类型名称都是区分大小写的。
All USES of the name must match and the name is case-sensitive.
对名称的全部使用都必须匹配并且名称是区分大小写的。
Remember that when you enter your username, it is case-sensitive!
记住，当你输入用户名，它对大小写是敏感的。
The attribute name is case-sensitive, and its data type should be an integer.
属性名称有大小写的区别，且数据类型应为整数。
Repeat Step 5 for the request queue, specifying the following case-sensitive values.
为请求队列(request queue)重复步骤5，指定下列值(区分大小写)。
Tip: The same script creates indexes for both case-insensitive and case-sensitive queries.
提示：相同的脚本可以同时为区分大小写的和不区分大小写的查询创建索引。
If Samba doesn't use case-sensitive access, then it is unable to differentiate between the two files.
如果Samba以大小写无关的方式访问它们，则无法区分这两个文件。
The first child node returns results that satisfy a case-sensitive like operation on the networkId attribute.
第一个子节点返回满足networkId属性上的大小写敏感的like操作的结果。
When you create the index for each field, you can decide whether queries will be case-insensitive or case-sensitive.
当您为每个域创建索引时，您可以决定查询是否要支持区分大小写。
For this example, the search string is also converted to lowercase, resulting in a search that is not case-sensitive.
在这个例子中，搜索字符串还被转换成小写字符，因此这个搜索不是大小写敏感的。
Note that these comparisons are also case-sensitive. To do a case-insensitive comparison use a command similar to this one
注意这些比较也是大小写敏感的。
Now it would seem fairly trivial to map from case-sensitive to case-insensitive, but in fact it's hard to do it efficiently.
从区分大小写映射到不区分大小写现在看来是很微不足道的，但实际上很难有效地进行这一映射。
Because XQuery is case-sensitive, lowercase table and column names would fail to match upper-case names in the DB2 catalog.
由于XQuery是大小写敏感的，因此小写的表名和列名不能与DB 2编目中的大写名称相匹配。
When it compares class names and attribute names, it looks for uniqueness in its container and USES case-sensitive comparisons.
在比较类名和属性名时，API会寻找容器内的单值，并区分大小写。
The default for this setting is auto, which looks for a client extension field to indicate that the client supports case-sensitive access.
该设置的默认值是auto，它会寻找一个客户端扩展字段来指示客户端是否支持区分大小写的访问。
For example, the index extension for the inverted text index can be parameterized to also support case-sensitive and case-insensitive indexes.
例如，将反向文本索引的索引扩展参数化，以支持大小写敏感和大小写不敏感的索引。
You should be aware that in deference to case-sensitive languages, all references to a definition must use the same case as the defining occurrence.
应该注意根据区分大小写的语言，所有的定义引用必须与定义的大小写相同。
When comparing operations, it performs a case-sensitive name match along with a comparison of input argument data types, and ignores return types.
在比较操作的时候，API会比较名称（区分大小写）以及输入参数数据类型，并忽略返回值类型。
In each XML file, you'll find a similar case-sensitive target statement that specifies where the content belongs in the navigation of a solution information project.
在每个XML文件中，都能发现一个类似的区分大小写的目标语句，这个语句指定了内容属于解决方案信息项目导航中的哪个位置。
Incidentally, notice that DCMI vocabulary terms are not case-sensitive, since they will often be used in case-insensitive contexts such as HTML (pre-XHTML, that is).
顺便说一下，DCMI词汇表术语是大小写不敏感的，因为常常被用于大小写不敏感的上下文，如HTML(即XHTML的前身)。
It's possible, as shown above, to write a rename rule that converts case-sensitive files into lowercase file names, thereby causing clashes among previously unique file names.
如上所述，可以编写一条重命名规则将区分大小写的文件名转换为小写文件名，这样可能会与以前已存在的唯一的文件名发生冲突。
To check the performance difference between queries in case-sensitive and case-insensitive databases, we created a regular database (case sensitive) and a case-insensitive database.
为了查明区分大小写的和不区分大小写的数据库之间的性能差异，我们创建了一个常规数据库（区分大小写）和一个不区分大小写的数据库。
This check is also case sensitive.
此检查也是区分大小写的。
Requests and responses are case sensitive.
请求和响应是区分大小写的。
Filter values are case sensitive.
过滤值是区分大小写的。
Note that the filter is case sensitive.
请注意过滤器是区分大小写的。
应用推荐