XML validation check constraints.
XML验证检查约束。
Step 2: Check constraints on object argument.
第2步：检查对象参数约束。
Check constraints are parsed but not enforced.
对检查约束进行解析，但是不强制实施。
Check constraints can also list a set of schemas.
检查限制还可以列出一组模式。
DB2 V9.5 supports check constraints for XML values.
DB 2 V 9.5支持对xml值进行检查约束。
Primary key, referential integrity, and check constraints.
主键、引用完整性和检查约束。
A user can enforce validation on an XML column using check constraints.
用户可以使用检查约束来加强对xml列的验证。
Some databases have different functionality for check constraints.
某些资料库有不同的检查条件约束功能。
Unlike CHECK constraints, DML triggers can reference columns in other tables.
与CHECK约束不同的是，dml触发器可以引用其他表中的列。
The check constraints view allows you to create table check constraints for the table.
允许您为表创建表检查约束。
The Check constraints view allows you to create table check constraints for the table.
Check constraints视图允许为表创建表检查约束。
Check constraints view a "Allows adding check constraints for a table and its columns."
Check constraints视图—允许添加表及其列的检查约束。
Triggers, unlike referential and check constraints, can even be used to update other tables.
触发器并不像参照完整性约束和检查约束那样，我们甚至可以使用对其他表来进行更新。
Another alternative is to specify partitioning predicates by defining check constraints on nicknames.
另一种方法是通过在昵称上定义检查约束来指定分区谓词。
Consult your database documentation for details about how your database works with check constraints.
如需资料库如何使用检查条件约束的详细资讯，请参阅资料库文件。
You have the ability to set extended properties using the Check Constraints properties user interface.
可以使用Check Constraints用户界面来设置扩展属性。
Both tables ITEMS and SUPPLIERS have check constraints defined on columns item_id and suppl_id respectively.
表items和SUPPLIERS分别在列item_id和suppl_id上定义了检查约束。
Design attribute domain integrity. Considerations include CHECK constraints, data types, and nullability.
设计域完整性属性。考虑CHECK约束，数据类型和是否非空。
Check constraints are constraints on table columns that are used to restrict the user to a particular check condition.
检查限制是表的列上的限制，用于将用户限制到特定的检查条件。
For our second strategy (one table per class hierarchy), you'll have to define your integrity using check constraints.
对于第二个策略(每个类层次结构一个表)，您必须用检测约束定义您自己的完整性。
In Part 1 of this article series, the example scenario defined the following set of informational check constraints.
在本系列的第1部分，示例场景定义了以下一组信息约束。
Clearly the use of check constraints has a minor effect on performance, but foreign keys and triggers can be extremely significant.
显然，检查约束的使用对性能有一点小小的影响，但是外键和触发器的影响却非常大。
Similar to the before trigger, the IS VALIDATED ACCORDING TO XMLSCHEMA clause can be used in the check constraints to enforce the validation.
与beforetrigger类似，可以在检查约束中使用ISVALIDATEDACCORDINGTO XMLSCHEMA 子句来加强验证。
SYSCAT.TABLES CHECKCOUNT Number of check constraints defined on this table db2 "select tabname, checkcount from syscat.tables where checkcount > 0"
TABLESCHECKCOUNT 该表所定义的检查约束的数量db2 "select tabname, checkcountfrom syscat.tableswhere checkcount > 0"
Optionally, CHECK constraints can be defined on the pdbxml table to ensure that the four-character PDB identifier conforms to the PDB standard.
或者，在pdbxml表中定义CHECK 限制以确保这个四字符的PDB标识符符合 PDB 标准。
Given the remote table definitions for items and suppliers, you can declare check constraints on the corresponding nicknames with the following commands.
给items和suppliers的定远程表定义，便可以用以下语句声明相应昵称上的检查约束。
In this case, the check constraints defined on nicknames canada.items and usa.items will allow the rewrite phase to eliminate one of the UNION all branches.
在这里，定义在昵称canada . items和us a . items上的检查约束将允许重写阶段删除其中一个UNION ALL分支。
You can also use the system catalog views to retrieve information about NOT NULL, unique, primary key, foreign key, and table check constraints. For example.
也可以使用系统编目视图来检索关于NOT NULL、惟一、主键、外键和表检查约束的信息。
The rewrite phase will use the referential and check constraints defined on the four nicknames to eliminate the join operations and one of the UNION branches.
重写阶段将使用四个昵称上定义的引用约束和检查约束来删除连接操作和一个UNION分支。
For example, tables may depend on user-defined distinct types; check constraints depend on functions; views depend on views, aliases, and functions; and so on.
例如，表可能依赖于用户定义的不同类型；检查约束依赖于函数；视图依赖于视图、别名和函数；等等。
应用推荐