现在需要的是更深层次的验证——在数据库层次。
What you need is a deeper level of validation — at the database level.
模型通过在数据库层次上设置优先级解决了这个问题。
This is addressed by the model by setting priorities at the chunk level.
数据集提供了很多好处，例如比起数据库层次，它强化了内存中的完整性规则。
Data set provided a lot of benefit, for example compared with database administrative levels, its aggrandizement the integrality in memory is regular.
这一共同的场景强调了重要的需要：支持更好的之间的互操 作性J2EE和数据库层次、IT 部门必须行动更快速、果断行动。
This common scenario highlights a significant need: to support better interoperability between the J2EE and database tiers, IT departments need to be able to act more quickly and decisively.
尽管XML在内部存储为层次化格式，但逻辑上，在数据库表中，它似乎存储在CLOB或BLOB中。
Although internally the XML is stored in a hierarchical format, logically in the database table it appears to be stored in a CLOB or BLOB.
这就要求数据库的适应性要达到一个新层次。
在每个数据库中，快照监控器基于表3中所示的功能组层次收集信息。
Within each database, the snapshot monitor collects information based on the functional group levels shown in Table 3.
只有展开到枝叶层次的元素，你才能开始把它映射到数据库的列。
It is only when you get to the leaf level elements that you can start mapping to columns in databases.
通过此技巧，您可以有效地在调用栈的较低层次开始事务，从而减少花费在数据库中的时间。
With this technique, you are effectively starting the transaction at a lower level in the call stack, thereby reducing the amount of time you are in the database.
对象数据库(ODBMS)在某些方面退回到了层次模型。
Object databases (ODBMSs) in some ways go back to the hierarchical model.
针对单个问题的优化：本质上，层次数据库就通过一条指定的路径来优化数据访问。
Optimized for one problem: By their nature, hierarchical databases optimized access to the data through one specific path.
在层次数据库(HDBMS)中，首先是从严格定义的数据节点树开始的。
In a hierarchical database (HDBMS), you begin with a strictly defined tree of data nodes.
对于物理记录的处理：层次数据库中所存储的记录是由应用程序来直接操纵的。
Deals with physical records: The records stored in hierarchical databases are manipulated directly by an application.
这会有利于层次、网络和对象数据库。
由于组件测试处理一个架构的多个层次，所以它们经常用于处理数据库、文件系统、网络元素等。
Because component tests deal with multiple layers of an architecture, they often deal with databases, file systems, network elements, etc.
就其性质而言，关系数据库比层次数据存储结构(如xml)更灵活。
Relational databases are, by their nature, more flexible than hierarchical data storage structures such as XML.
层次和对象数据库满足特定需求。
从广义角度来说，数据库管理系统(DBMS)在历史上划分成三种类型：层次、关系和面向对象。
In broad themes, database management systems (DBMSs) have historically been of three types: hierarchical, relational, and object-oriented.
它能够以关系数据库系统中的层次格式在本机存储XML数据。
It provides the ability to natively store XML data in its hierarchical format within a relational database system.
在第二个例子中，由于服务器管理层次的不当数据库备份而导致JournalSpace可以说是消失(或者我应该称之为被改写)。
In the second example, JournalSpace was literally written (or should I say overwritten) out of existence due to improper database backups on the server admin level.
一般而言，层次数据库兴起于 60年代，用在当时的大型机数据处理技术方面。
Generally speaking, h ierarchical databases arose in the 1960s, on the mainframe data processing technology of the time.
除了函数，这两种数据库还允许您创建新的类型，以及通过使用表层次结构创建对象层次结构。
In addition to the functions, these databases allow you to create new types and create object hierarchies through the use of table hierarchies.
在参与分布式查询的所有数据库中，各种数据类型必须定义有相同的层次结构和类型转换。
The distinct data types must have exactly the same hierarchy and casts defined in all databases participating in the distributed queries.
企业百科全书是拥有基于角色控制以及实例层次控制的数据库。
Enterprise encyclopedias are databases that have role-based access control and instance-level access control.
安全管理员可以在接近于组织结构的抽象层次上控制对数据库的访问。
Security administrators can control access to their databases at a level of abstraction that is close to the structure of their organizations.
我们可以通过标准的关系方法或使用新的数据类型，在数据库中表示该层次结构关系。
We can represent this hierarchical relationship in the database through standard relational methods or using new data types.
它可以保持其层次化性质，同时利用关系数据库环境的功能和稳定性。
It proudly maintains its hierarchical heritage, even while exploiting the power and stability of the relational database world.
创建一个数据库时，关于数据库的信息，包括默认信息，存储在一个目录层次结构中。
When a database is created, information about the database, including default information, is stored in a directory hierarchy.
宏观层次就是构建和应用范围，而微观层次处于领域层，领域类在与数据库发生交互时发布事件。
The macro level is build and application wide and the micro level happens at the domain layer, where domain classes publish the events whenever they interact with the database.
与表4中的数据相联系，可以指示数据库服务器是系统中最少使用的构件，数据库通道也可以提供最高层次的性能。
Correlated with the data in Table 4, which indicates that the database server is the least-used component in the system, either database vendor will provide the highest level of performance.
应用推荐