[OASIS Issue Tracker] (ODATA-959) Allow path in an edm:key to also use a primitive property of a non null-able navigation property (recursively) of the entity type.

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

Hubert Heijkers created ODATA-959:
-------------------------------------

             Summary: Allow path in an edm:key to also use a primitive property of a non null-able navigation property (recursively) of the entity type.
                 Key: ODATA-959
                 URL: https://issues.oasis-open.org/browse/ODATA-959
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Improvement
          Components: OData CSDL
    Affects Versions: V4.0_ERRATA03
            Reporter: Hubert Heijkers
             Fix For: V4.01_WD01


Currently a key can only be made up of properties that are either in the entity type directly or in a complex property recursively. It therefore explicitly excludes the use of these properties in a, non null-able, navigation property. This causes the modeler to expose the underlying data structure as he'll have to add these primitive properties to the entity directly and keeping them in sync using referential constraints.
An example that shows this would be a situation like in graphs where nodes are connected by edges and where an edge gets particular properties associated to it. Here the edge will have to, apart from the two navigation properties representing the nodes it is connecting also two primitive properties that contain the node IDs to be able to form a key for an edge.
Obviously many m-n relationships exist which have additional properties describing the relationship exist that would benefit.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)