Mode i: Turn on case insensitive matching.
模式i：打开不区分大小写匹配。
It does not require an exact match and is case insensitive.
它不要求精确匹配，也不区分大小写。
Avoid case insensitive searches unless absolutely necessary.
除非绝对必要，否则应该避免大小写不敏感的搜索。
Note that runmqsc parameters are case insensitive unless quoted.
注意，除非用引号括起来，否则runmqsc参数不区分大小写。
It is case insensitive, and bootcontrol.pl selects the first matching instance.
该参数是不区分大小写的，bootcontrol . pl会选择第一个匹配的实例。
The mode i turns on case insensitive matching, while inm turns on those three options.
模式i打开不区分大小写匹配，而inm 打开三种选项。
Although URI schemes are case insensitive, the tag RFC (see Resources) recommends the lower-case form.
虽然uri方案对大小写不敏感，但是标签RFC(请参阅参考资料)建议采用小写形式。
The mapping is case insensitive and only matches if the method has a return value and no input parameters.
映射区分大小写，只有当方法拥有一个返回值而且没有输入参数时才能匹配。
Therefore you must go through the entire process for enabling case-insensitive queries for every user database.
因此您必须经历为每个用户数据库激活不区分大小写查询的整个过程。
Indicate that the index should be case-insensitive.
这表明索引应该是不区分大小写的。
Since only mappings between EJB fields and table fields with the same (case-insensitive) name can be done automatically, these must be done by hand.
由于ejb字段和表字段之间只有名称相同(不区分大小写)才能自动完成映射，因而这些必须手动完成。
There are several methods to search DB2 data in a case-insensitive manner such as the use of generated columns (see Resources).
以不区分大小写的方式搜索DB 2数据有多种方法，比如使用生成的列(请参见参考资料)。
To begin the process of enabling case-insensitive queries, review the schema of the user database and identify all of the multiline text fields.
要开始激活区分大小写查询程序的过程，首先要复审用户数据库的模式，并确定所有的多行文本域。
If you no longer want to enable case-insensitive queries on any field in the table, you can disable indexes for the entire table.
如果您不再想在这个表格的任何一个域上激活不能区分大小写查询程序，您可以使整个表格的索引功能失效。
Now it would seem fairly trivial to map from case-sensitive to case-insensitive, but in fact it's hard to do it efficiently.
从区分大小写映射到不区分大小写现在看来是很微不足道的，但实际上很难有效地进行这一映射。
However, not all queries need to be case-insensitive.
然而，并不是所有的查询都需要是区分大小写的。
The potential drawback of the approach described in this section is that all the data in all the columns in all tables in the entire database are treated in a case-insensitive manner.
本节介绍的方法有一个潜在的缺点：整个数据库中所有表中的所有列中的所有数据都是不区分大小写的。
An application that queries these XML documents to find customers with a specific city most likely requires case-insensitive search.
如果一个应用程序查询这些XML文档，寻找某一城市的客户，那么很可能需要不区分大小写的搜索。
Internally, DB2 processes user ID and group names in a case-insensitive fashion.
在内部，DB 2以不区分大小写的方式处理用户ID和组名。
When you create the index for each field, you can decide whether queries will be case-insensitive or case-sensitive.
当您为每个域创建索引时，您可以决定查询是否要支持区分大小写。
For example, the index extension for the inverted text index can be parameterized to also support case-sensitive and case-insensitive indexes.
例如，将反向文本索引的索引扩展参数化，以支持大小写敏感和大小写不敏感的索引。
To create a database that is case-insensitive for all string comparisons, it is necessary to use the collation UCA500R1 as shown in Listing 4.
要想创建对于所有字符串比较不区分大小写的数据库，需要使用排序规则UCA500R1，见清单4。
In the case of an E-mail address, you might want to perform a case-insensitive search.
在使用电子邮件地址时，可能想执行不区分大小写的搜索。
In other words, string comparisons may be slightly more expensive in a case-insensitive database.
换句话说，在不区分大小写的数据库中，字符串比较的开销可能会略微增加。
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的前身)。
If you begin a subpattern with the modifier (? I), matching in the subpattern is case-insensitive.
如果子模式以修饰词(？i)为开头，则在子模式中进行匹配不区分大小写。
Parameter names are case-insensitive.
参数名是不区分大小写的。
However, not every multiline text field needs to support case-insensitive queries.
然而，也并不是每一个多行文本域都需要支持区分大小写的查询。
Such queries took 5% to 8% longer in the case-insensitive database.
在不区分大小写的数据库中，这种查询花费的时间增加了5%到8%。
Tip: The same script creates indexes for both case-insensitive and case-sensitive queries.
提示：相同的脚本可以同时为区分大小写的和不区分大小写的查询创建索引。
应用推荐