[OASIS Issue Tracker] (ODATA-1132) Propagation of NavigationRestrictions

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

    [ https://issues.oasis-open.org/browse/ODATA-1132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=68906#comment-68906 ] 

Michael Pizzo edited comment on ODATA-1132 at 1/25/18 5:56 PM:
---------------------------------------------------------------

Minimally, we would need a navigationpropertybinding to specify that the Customers navigation property was tied to the Customers entity set.

Even in that case, there could be situations, for example, where the Customers entity set could only be queried if the Order Id was known (for example, a federated database, an index containing OrderId, or a backing webservice that requires the order id be specified).

These are the exception cases, though. 

Question: what is the cost of putting the restriction in multiple places, versus the complexity of the client having to do the aggregation of effective restrictions?


was (Author: mikep):
Minimally, we would need a navigationpropertybinding to specify that the Customers navigation property was tied to the Customers entity set.

Even in that case, there could be situations, for example, where the Customers entity set could only be queried if the Order Id was known (for example, a federated database, an index containing OrderId, or a backing webservice that requires the order id be specified).

These are the exception cases, though. 

> Propagation of NavigationRestrictions
> -------------------------------------
>
>                 Key: ODATA-1132
>                 URL: https://issues.oasis-open.org/browse/ODATA-1132
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: Vocabularies
>    Affects Versions: V4.0_CSD01
>            Reporter: Ralf Handl
>             Fix For: V4.0_CSD02
>
>
> Clarify whether/how navigation restrictions "propagate".
> Assume we have 
> - Order entity related to single Customer entity
> - Customer entity related to multiple Address entities
> - a navigation restriction on Customers entity set which lists Addresses as filterable:false.
> Now a client knows that it cannot filter Customers by Addresses.
> Should a client assume that it also cannot filter Orders by Customer/Addresses?
> Or would the service have to explicitly declare navigation restrictions for all entity sets with navigation paths ending in Customer/Addresses?



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