Without an identifier, there is no way to represent an entity as metadata.
如果没有标识符，我们就没有办法把这个实体表现为元数据。
If it applies to the current transition and entity, the plug-in will undertake the required validation, adding metadata where required.
如果适用于当前的转换和实体，则插件将执行必需的验证，并在所需的地方添加元数据。
For better readability, the relationships in our scenario are expressed through object or relational metadata specified directly in the entity class files.
为了提高可读性，通过在实体类文件中直接指定的对象或关系元数据表达场景中的关系。
The metadata items are then simple properties of this entity.
元数据术语就是该实体的简单属性。
By choosing the preferred display form as the representation of the entity your metadata has a fatal flaw: any change to the display form creates a different entity.
你可以选择一种首要的显示方式来表现某个实体，但是你的元数据因此就有了一个致命的错误：只要现实的形式发生了变化，也就出现了一个不同的实体。
The query and metadata caching results in the second run always executes faster than the first run. For example, looking at this Entity SQL query.
由于查询与元数据缓存的存在，使得第二次运行的执行速度总是比第一次运行快。
To add the Sales Order entity to the metadata file.
在元数据文件中添加销售订单实体。
You learned about the entity and metadata types that comprise Registry and Repository content model.
您了解了构成Registry andRepository内容模型的实体和元数据类型。
In this sample Message Broker flow shown in Figure 13, the SRRetrieveEntity node is used to retrieve all metadata contents for a specific entity.
在图13中所示的此示例Messagebroker流中，SRRetrieveEntity节点用于从特定实体检索所有元数据内容。
If you don't add any additional metadata, Hades will try to lookup a JPA named query of the form {entity}. {method-name} and use that if available.
如果你没有增加任何附加的元数据，Hades会尝试查找格式为{entity}. {method - name}的JPA查询方法，如果有效的话就使用该方法。
Figure 4 Sample Entity — Atlas Metadata representation.
图4样例实体——Atlas元数据表示。
The three metadata structure of organizational management was adopted: metadata section, metadata entity, and metadata element.
采用元数据组织管理的三层体系结构：元数据子集、元数据实体和元数据元素。
The three metadata structure of organizational management was adopted: metadata section, metadata entity, and metadata element.
采用元数据组织管理的三层体系结构：元数据子集、元数据实体和元数据元素。
应用推荐