字符比较用英语怎么说，字符比较的英文翻译

词语导航

基本信息

词语：字符比较

繁体：字符比較

拼音：zì fú bǐ jiào

英语翻译

【计】 character comparison

分词翻译

字符的英语翻译：

【计】 C; CH; character

比较的英语翻译：

compare; assimilate; confront; comparison; comparatively; relatively
【计】 compare; match
【医】 cf.; confero
【经】 compare; comparison

翻译例句

1. 我怎样使用通配字符比较字符串？

How do I compare strings using wild CARDS?

2. 我怎样使用通配字符比较字符串？

How do I compare strings using wildcards?

3. 查询编译器在检查字符比较操作时使用该信息，以决定如何执行操作。

The query compiler uses this information while checking any character comparison operations, to decide how to evaluate the operations.

4. 在后两个 if之前添加else，即可避免不必要的字符比较。

You can add else before the later two ifs to avoid unnecessary character comparison.

5. 显然使用逐字符比较的标准排序法肯定会说两者不同，因此需要使用自定义的排序法。

Obviously a character-by-character comparison using the standard collation says these are not equal, so you"ll need to use a custom collation.

6. 这个例程检查字符是否在A到Z之间，然后将其转换为小写字母并将它直接和其他字符比较。

This routine checks to see if a character is between a and Z, then converts it to lowercase and compares it; it compares other characters directly.

7. 当你这样做时，可以这样说，你在你的大脑建立一个了“查询表”，每一个字符与你查询表中的字符比较，直到找到匹配的。

When you do it this way, you build a "lookup table" in your brain, comparing each character you hear with those in the lookup table until you find a match.

8. 和西班牙语排序法一样，只要定义比较字符的规则即可。

As with the Spanish collation, you simply define rules that say how to compare characters.

9. 在DB 2UDBV8.2之前，Unicode数据库只能定义为排序次序identity，这意味着按照字节编码对字符进行比较。

Prior to DB2 UDB V8.2, a Unicode database could only be defined with the collating sequence IDENTITY, which means that the characters are compared by their byte encoding.

10. 面向字符的流比较单调，只提供两种格式。

The character-oriented streams are less dramatic, providing just two formats.

11. 这里不需要调用一个字符一个字符地进行比较的equals函数，相反，您可以通过引用将解析器报告的名称与字符串常量进行比较。

Instead of making calls to equals which compares strings character by character, you can compare names reported by the parser against string constants by reference.

12. 这可以确保在查询中使用日期比较，而不是标准的字符串比较。

This ensures that the date comparison is used in the query, rather than standard string comparison.

13. 在查询运行时，尝试在雇员ID上执行字符串比较将遭到失败，并产生一个类型错误。

Any attempt to perform a string comparison on an employee ID will then fail with a type error at query run time.

14. 强度属性决定在对文本字符串进行排序或比较时，是否考虑重音或大小写。

The strength attribute determines whether accent or case is taken into account when collating or comparing text strings.

15. 第二个属性s2指定强度级别，这决定在字符串排序或比较时是否考虑大小写或重音符号。

The second attribute S2 specifies the strength level which determines whether case or accent is taken into account when ordering or comparing strings.

16. 例如，假设您并不想对属性名和字符串模式进行比较，而只是想查明具有该属性名的属性是否一直保存在持久性数据库中。

For example, perhaps you do not simply want to compare the attribute name to a string pattern, but actually look up whether the name is an attribute that has been stored in a persistent database.

17. 所以在使用了命名空间的文档中，您几乎总是需要进行两次字符串比较，如清单3所示。

So in namespaced documents, you almost always need to perform two string comparisons, as shown in Listing 3.WWW.wEntIyI.coM

18. 使用该方法验证的关键在于将更新过的索引和初始输入字符串的长度进行比较。

The key to using the method for validation is to compare the updated index to the length of the original input string.

19. 对字符串数据进行比较并按一定顺序排列的过程称为排序。

The process of comparing string data and placing it in order is known as collation.

20. 清单15、清单16和清单17分别演示如何使用文件、数字和字符串比较。

Listing 15, Listing 16, and Listing 17 display how you can use numeric, string, and file comparisons, respectively.

21. 对于输入不知道的字符，或是难于输入的字符(例如长的包括字母和数字的字符)是比较棘手的。

It is troublesome to try to enter Strings that you do not know offhand, or that would be difficult to type, like long alphanumeric Strings.

22. 算法很简单，它对树的顶级项目进行迭代，并将其文本内容与搜索字符串进行比较(清单6中的第43- 52行)。

The algorithm is simple; it iterates through the top-level items of the tree and compares their text contents with the search string (lines 43 to 52 in listing 6).

23. 当然，正则表达式被限定为严格的字符串比较。

Of course, regular expressions are limited to strict string comparisons.

24. 强烈推荐对所有字符串比较使用“显式设置大小写的”运算对象，因为这样可以确保无论用户选项设置如何变化，脚本都可以可靠地执行。

Using the "explicitly cased" operators for all string comparisons is strongly recommended, because they ensure that scripts behave reliably regardless of variations in the user"s option Settings.

25. 我们发现涉及大量行的查询的性能差异比较大，比如对所有20,000个XML文档进行全表扫描并对每个文档比较字符串。

We found a bigger difference for queries that touch a large number of rows, such as a table scan over all 20,000 XML documents with string comparison on every document.

26. 经过实验，我还发现循环字符串比较操作速度都非常快。

Experimentally, I also found that a looping string comparison is faster than taking a slice.

27. 正如您看到的，使用强类型资源类访问资源文件中的字符串比较简单。

As you can see, accessing strings from a resource file using a strongly typed resource class is pretty easy.

28. 要想创建对于所有字符串比较不区分大小写的数据库，需要使用排序规则UCA500R1，见清单4。

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.

29. 换句话说，在不区分大小写的数据库中，字符串比较的开销可能会略微增加。

In other words, string comparisons may be slightly more expensive in a case-insensitive database.

30. 换句话说，在不区分大小写的数据库中，字符串比较的开销可能会略微增加。

In other words, string comparisons may be slightly more expensive in a case-insensitive database.