EOS unidirectional N-to-1 association

1.

The attribute used in the N-end entity can be a primary key or a non-primary key, andthe associated field on the 1 side must be a primary key (either Tanki or a composite primary key).

such as the associated field: OrgID

2.
When the properties used for correlation are selected on the N-side, these properties are not present in the N-side entities and are inaccessible and are replaced with 1 1-side entities. when you want to access N-end the value of these attributes, you need to manipulate the primary key properties of the 1-side entity.

3.
A one-way N:1 Association is supported for lazy loading. If the delay load is set to False, indicating that lazy loading is not supported, then query the N-side entity at the same time the 1-side entity, the query is a sentence joinsql query, if the setting delay load to true, indicating that support lazy loading, first detect all the N-side entities, The 1-terminal entity is then queried based on the N-side correlation attribute.

EOS unidirectional N-to-1 association