Skip to content

Commit 3d40504

Browse files
committed
be more precise on the default cardinality context
Reading the "managed composition" part made me first think of the Orders:Items element when talking about the cardinality, but that's to-many, which had me wondering for a sec. But I think what's being referred to here is the backlink, i.e. this `up_` element: ```yaml Orders.Items: kind: entity includes: [OrderItems] elements: up_: key: true type: cds.Association cardinality: { min: 1, max: 1 } target: Orders keys: [{ ref: [ID] }] notNull: true ```
1 parent c83fdfe commit 3d40504

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

cds/cdl.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1040,7 +1040,7 @@ aspect OrderItems {
10401040

10411041
#### Default Target Cardinality
10421042

1043-
If not otherwise specified, a managed composition of an aspect has the default target cardinality *to-one*.
1043+
If not otherwise specified, a managed composition of an aspect has the default target cardinality *to-one* for the backlink.
10441044

10451045
#### For Many-to-many Relationships
10461046

0 commit comments

Comments
 (0)