The intent of this restriction was twofold.
这种限制的意图是双重的。
This restriction not only contributed to Great Britain's rise as Europe's foremost shipping nation but also laid the foundations for an American shipbuilding industry and merchant marine.
这一限制不仅促成了英国作为欧洲最重要的航运国家的崛起，也为美国的造船业和商船奠定了基础。
Examples of this restriction include the following.
此限制的示例包括以下情况。
This restriction allows internal packages to stay internal.
该限制允许内部包保留在内部。
This restriction is due to the coil of the contactor used.
此限制是由于所使用的接触器的线圈。
You can overcome this restriction by using parallel access volumes (PAVs).
可以通过使用并行访问卷克服这个限制。
This restriction was true even if the XML data included only ASCII code points.
即使XML数据中只包含ASCII代码点，这个限制也仍然有效。
Observe the implications of this restriction when testing your stored procedure.
请在测试存储过程时观察这一限制的影响。
You might consider implementing this restriction on your multi-user systems as well.
您也可能会考虑在自己的多用户系统中实现这种限制。
This restriction is a significant limitation of ADB, but also confers some advantages.
这个限制是ADB的一大局限，但也带来了一些好处。
(You can lift this restriction by using a more advanced JMX feature, dynamic MBeans.)
可以用更高级的jmx特性——动态mbean来去除这个限制。
No other formats discussed in this article— DXF, DWG, and KML— have this restriction.
而本文中所讨论的其他格式 DXF、DWG和 KML均没有这个限制。
Let's run the advisor again and remove this restriction to see if we get a better result.
让我们再次运行Design Advisor，并去掉这个限制，看是否可以获得更好的结果。
This restriction reduces the scalability of the system when multiple gateways are required.
当需要多个网关时，这种限制减低了系统的可伸缩性。
This restriction is easily done by defining the android:permission attribute as in Listing 4.
通过像清单 4中那样定义android:permission属性，很容易实现这种限制。
Some repositories, particularly those without true item classes, do not have this restriction.
某些存储库，尤其是那些没有真正项目类的存储库，没有这种限制。
In summary, this restriction makes it easier to implement a JMS provider as a JCA resource adapter.
总之，这种限制使得JMS提供者更容易实现为JCA资源适配器。
Without this restriction, maintaining uniqueness across multiple range partitions would be impractical.
如果没有这一限制，就无法维护跨越多个分区的唯一性。
This restriction is mitigated by using an industry standard binding, such as Web Services, JMS, and so on.
通过使用Web服务、JMS等行业标准绑定可以减轻此限制的影响。
DB2 V9.5 removes this restriction and allows a user to create the database with an XML column in any code set.
DB 2V9.5去掉了这个限制，并且允许用户用任意代码集创建包含xml列的数据库。
We believe, from the point of information integrity, this restriction can be relaxed to reversible matrix.
我们认为，从信息完整的角度考虑，可以将这个条件放宽到可逆矩阵。
The specification provides no explanation as to why this restriction has been added, but I'll give you my theory.
规范没有解释为什么会增加这个限制，不过我将给出我的理论。
DB2 V9.5 lifts this restriction, and now users can annotate and decompose the data even when the schema is recursive.
DB 2V9.5解除了这个限制，现在即使模式是递归的，用户也可以对数据进行注释和分解。
This restriction is already followed with the general topic migration, so no new processing is needed for concept topics.
这一限制在一般主题迁移中已经遵守了，因此概念主题不需要新的处理方法。
Keep this restriction in mind if you are faced with the challenge of supporting multiple locales within these environments.
如果您面临在这些环境中支持多个语境的挑战，请记住这个限制。
This restriction doesn't have the same potential pitfalls as what we just discussed, but it can make your code pretty wordy.
和我们刚才讨论的不同，这一限制没有同样的潜在缺陷，但它会使您的代码非常冗长。
As you saw in part 2 of this series, this restriction means that you must put items like database code in other parts of your system.
正如您在本系列的第2部分中所见，此限制意味着必须将诸如数据库代码之类的条目置入系统的其他部分中。
Before Milnor, no one had any inkling that this restriction made any difference; for spaces of three dimensions or fewer, it does not.
在米尔诺尔之前，没有人认为这个限制有什么影响；而对于三维以下的空间，确实没有影响。
This restriction is lifted in Groovy; you can change the values of variables in a containing scope from within an anonymous inner class.
Groovy则消除了这种限制，在Groovy中，匿名内部类可以修改外部的变量值。
Please follow the "Restrictions on MQTs over nicknames in a partitioned database environment" for tips on how to work around this restriction.
请参考“分区数据库环境中的MQT优于昵称限制”，了解关于如何处理该限制的提示。
应用推荐