全部

1·Type mismatch: Cannot convert into .

类型不一致，不能完成转换。

2·Type mismatch between proxy type {0} and activation type {1}.

代理类型 {0} 和激活类型 {1} 之间的类型不匹配。

3·Using master replicates avoids runtime data corruption occurring due to data type mismatch on source and target nodes.

通过使用主复制，可以避免在运行时发生由于源节点与目标节点之间的数据不匹配而导致的数据损坏。

4·We think this advantage is often oversold, as type mismatch errors are a small fraction of the runtime errors you typically see.

我们通常认为这个优势被夸大了，因为类型不匹配的错误只是日常见到的运行时错误中的一小部分。

5·Preventing data type mismatch between Enterprise Replication nodes helps avoid possible data corruption during replicate definition.

防止Enterprise Replication节点之间数据类型的不匹配，有助于避免复制定义期间数据被损坏。

6·If I try to specify something else, I'll either get a compiler issue or Hadoop will error-out with a message describing a type mismatch.

如果我想指定其他内容，将会出现一个编译器问题，或Hadoop将输出一个错误消息，描述类型不匹配的消息。

7·This may be due to an unset Orientation property for the axis or a type mismatch between the values being plotted and those supported by the axis.

这可能是因为轴线的一个未设置的Orientation特性或者所标绘的值与轴线支持的值之间存在类型不匹配。

8·The following example verifies that the tables included in the template exist on three servers, whether the primary key exists, if there is a data type mismatch, and so forth.

下面的例子检验模板中包括的表是否在三个服务器上，是否存在主键，是否存在数据类型的不匹配，等等。

9·However, a file type mismatch where the filesystem contains a plain file and the database records a device node is harmless; this is how pseudo emulates creation of device nodes.

不过，在文件系统包含纯文本文件时文件类型将不匹配并且服务器将记录设备节点，这不会产生不良影响；这就是pseudo模拟设备节点的创建方式。

10·In other words, when two class loaders load different classes (that is, different bytecodes) with the same name, class loader constraints guarantee that there will be no type mismatch between them.

换句话说，当两个类装入器用相同的名称装入不同的类时(也就是不同的字节码)，类装入器约束保证了它们之间不会有类型不匹配。