Compatible XML schema evolution.
兼容的XML模式演化。
Impact of XML Schema evolution on queries.
XML模式演化对查询的影响。
The sample code xsupdate.db2 demonstrates the compatible XML schema evolution.
示例代码xsupdate.db2演示了兼容的XML模式演化。
Now, let's look at how Rails migration can facilitate the database schema evolution.
现在，让我们看看Rails迁移如何为数据库模式变更提供帮助。
The reason the wildcard was added in the first place was to allow for schema evolution.
通配符添加于第一处的原因是为了允许模式改进。
On the opposite end, the plain XML user can do virtually nothing to manage schema evolution.
而与之相反的另一端，一般XML用户对于管理模式演化无能为力。
We discussed the impact of schema evolution on validation, query formulation, and results in detail.
我们详细讨论了模式演化对验证、查询公式和结果的影响。
In some cases of XML schema evolution, different namespaces denote different versions of the schema.
在XML模式演化的过程中，有时候用不同的名称空间表示不同的模式版本。
Specifically, for XML databases, schema evolution still is one of the demanding use cases for XML.
具体来说，对于XML数据库，模式演化是 XML的迫切要求。
This article has presented an extended taxonomy for changes that can happen during XML schema evolution.
本文提出了XML模式演化过程中变动的扩展分类。
In "taxonomy of XML schema changes," we present the taxonomy of changes that may happen during XML schema evolution.
“XML模式变化分类”一节提出了模式演化过程中可能出现的变化类型。
Coupling run amok prevents schema evolution, because other systems depend on your interfaces remaining consistent.
耦合的猖獗会阻止模式的改进，因为其他系统依赖于您的接口保持一致。
Rails migration does the job of the majority of the database administrative tasks associated with schema evolution.
通过Rails迁移完成模式变更这一主要的数据库管理任务。
We consider the most common types of changes that can happen during XML schema evolution and propose a taxonomy for them.
我们考虑了在XML模式演化过程中最常见的变化类型并提出了一种分类方法。
To increase the flexibility and provide better schema evolution, DB2 V9.5 introduces the update feature for an XML schema.
为了增加灵活性并提供更好的模式演化，DB 2V9.5为XML模式引入了update特性。
Probably the main drawback of JAXB, and of data binding in general, is that it makes schema evolution very cumbersome.
可能的主要缺点JAXB和一般意义上的数据绑定，是它使模式演化非常麻烦。
This paper addresses the problem by providing equivalent schema evolution (ESE) mechanism based on path independence (PI) program.
提出了基于路径无关语言的等价模式演化方案来解决这个问题。
Furthermore, the applications on top of the database and its users still need to interact with it regardless of its schema evolution.
另外，数据库之上的应用程序及其用户仍然需要和其交互，不论模式如何变化。
This work is not intended to exhaust the subject but rather to cover the most common situations an XML designer faces on schema evolution.
本文并没有介绍所有可能的情形，而是列举XML设计人员在模式演化过程中遇到的最常见的情形。
We'll provide techniques for managing these kinds of changes, without breaking existing pickles, in the Schema evolution section below.
我们会在下面模式改进这一节提供一些技术来管理这类更改，而不会破坏现有的pickle。
DB2 9.7 has relaxed its object dependency rules to allow for more flexible schema evolution. For example, assume you had the following dependency.
DB 2 9.7放宽了对象依赖规则，允许更灵活的模式演化。
An advantage of intact storage is that any schema evolution due to changes in the purchase order (additional information like shipping), is painless.
完整存储的好处是任何由于采购订单的变化(如运输等其他信息)而发生的模式演化都不会有什么影响。
For all these reasons, schema evolution is a very important topic that has been researched in the context of relational, object-oriented, and XML databases.
由于上述这些原因，模式演化作为一项重要课题需要在关系、面向对象和XML数据库环境中加以研究。
Schema evolution is a key problem in object-oriented systems because the dynamic nature of typical OODB applications calls for frequent changes in the schema.
模式演化是OO系统中一个很关键的问题。由于OODB的应用具有动态特征，因而模式要经常改动。
Of these four roles, the XML data and application architects have the most freedom in how they design their schema changes and applications to manage schema evolution.
在这四种角色中，XML数据和应用程序架构师对于如何设计模式变化和应用程序来管理模式演化具有最大的自由度。
We will also look into the effects of changes in the business requirements on the data (schema evolution) and its impact on the application code and the relational schema.
还将讲述业务需求更改对数据的影响(模式演化)以及对应用程序代码和关系模式的影响。
In this section, we'll discuss practical issues involved in controlling schema evolution and present a compact set of guidelines for writing queries across schema versions.
这一节讨论控制模式演化的实际问题，并提供出一组用于编写跨模式版本查询的指导原则。
The Rails migration feature helps application developers manage this schema evolution, making it easy to synchronize changes between the application code and the database objects.
Rails迁移特性可以帮助应用程序开发人员管理这种模式演变，便于在应用程序代码与数据库对象之间同步更改。
If "phone" was an attribute of the employee element, then it can exist only once per employee, and we could not add child elements too it, which may hinder schema evolution over time.
如果“phone”是雇员元素的一个属性，那么对于每个雇员，它只能出现一次，我们也不能为之添加子元素，这将妨碍模式随时间而变化。
Allows CREATE and DROP of arbitrary database objects, in conjunction with Hibernate's schema evolution tools, to provide the ability to fully define a user schema within the Hibernate mapping files.
帮助CREATE和DROP任意数据库对象，与Hibernate的sche ma交互工具组合起来，可以提供在Hibernate映射文件中完全定义用户schema的能力。
应用推荐