[ http://tools.oasis-open.org/issues/browse/ODATA-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ralf Handl updated ODATA-32:
----------------------------
Proposal:
From 2012-11-9 discussion:
We support the following operations in $expand (semi-colon separated):
-$filter
-$orderby
-$select
-$expand
-$inlinecount
-$top
-$skip
We no longer support paths in $select or $expand; you use nesting.
$select, if specified, limits the properties exposed regardless of inner expands, etc.
Accepted: https://www.oasis-open.org/apps/org/workgroup/odata/download.php/47432/latest/odata-meeting-15_on-20121108_9-F2F-minutes.html
was:
From 2012-11-9 discussion:
We support the following operations in $expand (semi-colon separated):
-$filter
-$orderby
-$select
-$expand
-$inlinecount
-$top
-$skip
We no longer support paths in $select or $expand; you use nesting.
$select, if specified, limits the properties exposed regardless of inner expands, etc.
> Allow filtering of expanded to-many navigation properties
> ---------------------------------------------------------
>
> Key: ODATA-32
> URL: http://tools.oasis-open.org/issues/browse/ODATA-32
> Project: OASIS Open Data Protocol (OData) TC
> Issue Type: New Feature
> Components: OData Protocol v1.0, OData URL Conventions v1.0
> Affects Versions: WD01
> Environment: [Proposed]
> Reporter: Ralf Handl
> Fix For: WD01
>
>
> "Give me all open purchase orders and expand all items that have a weight of over five tons"
> This cannot be expressed as a query on the items if these are contained in the orders.
> Even if the items are not contained, the reformulation as a query on items expanding the order would repeat the included order entities in case of multiple matching items, which is undesirable.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
