[OASIS Issue Tracker] (ODATA-560) Allow arbitrary properties in referential constraints

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

     [ https://issues.oasis-open.org/browse/ODATA-560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Pizzo updated ODATA-560:
--------------------------------

    Environment: Complex Types, [Proposed]  (was: Complex Types)
       Proposal: 
For 4.01 clients only, allow path expressions resolving to complex properties and navigation properties for the Property and ReferencedProperty attributes

Services must not advertise constraints terminating in a complex type or single-valued nav prop to clients specifying OData-MaxVersion:4.0, or those omitting the OData-MaxVersion header.

  was:Also allow path expressions resolving to complex properties and navigation properties for the Property and ReferencedProperty attributes


Note that, in this case, we can ensure backward compatibility by simply omitting the referential constraint for 4.0 clients. Not knowing about the referential constraint shouldn't break clients, having something unexpected in $metadata probably would.

> Allow arbitrary properties in referential constraints
> -----------------------------------------------------
>
>                 Key: ODATA-560
>                 URL: https://issues.oasis-open.org/browse/ODATA-560
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData CSDL
>    Affects Versions: V4.0_CS02
>         Environment: Complex Types, [Proposed]
>            Reporter: Ralf Handl
>            Assignee: Ralf Handl
>              Labels: Usability
>             Fix For: V4.01_WD01
>
>
> Referential constraints are currently limited to primitive properties, potentially nested within complex properties, which requires e.g. to "resolve" referential constraints between complex properties or single-valued navigation properties into one <ReferentialConstraint> element per primitive property of the complex property, and key property of the related entity type.
> An obvious generalization is to also allow complex properties, meaning that each member property has the same value, and as a consequence single-valued navigation properties, meaning that the dependent navigation property has the same target as the principal navigation property. This is just a short-hand notation for adding referential constraints on all leaf structural / key properties.



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