[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (ODATA-958) Capabilities: FilterRestrictions and SortRestrictions for navigation properties
[ https://issues.oasis-open.org/browse/ODATA-958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=67703#comment-67703 ]
Ralf Handl commented on ODATA-958:
----------------------------------
After this addition I wonder where I should annotate filter and sort restrictions for contained entities:
* FilterRestrictions and SortRestrictions on the containment navigation property (only way before applying this issue), or
* NavigationRestrictions on the "parent" entity set with the "container" entities
Which restrictions would apply to direct access to the contained set:
* GET Whole(42)/Parts?$filter=...&$orderby=...
Which restrictions would apply to nested query options within expand:
* GET Whole?$expand=Parts($filter=...;$orderby=...)
> Capabilities: FilterRestrictions and SortRestrictions for navigation properties
> -------------------------------------------------------------------------------
>
> Key: ODATA-958
> URL: https://issues.oasis-open.org/browse/ODATA-958
> Project: OASIS Open Data Protocol (OData) TC
> Issue Type: Bug
> Components: Vocabularies
> Affects Versions: V4.0_ERRATA02
> Environment: Annotations
> Reporter: Ralf Handl
> Assignee: Michael Pizzo
> Fix For: V4.01_WD01
>
>
> With the addition of cross-service navigation we need means to express that a navigation property cannot be used in filter or sort expressions.
--
This message was sent by Atlassian JIRA
(v6.2.2#6258)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]