[ http://tools.oasis-open.org/issues/browse/ODATA-36?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=31523#action_31523 ]
Michael Pizzo commented on ODATA-36:
------------------------------------
This seems really wrong to me.
The $select expresses a projection; it doesn't change the membership, just what is reported about each member. It is optional (the service can ignore the $select and pass additional fields.
$filter controls the membership and is not optional. If you specify $filter, you assume results meet the specified criteria and if the service returns additional results then client side logic is likely to make bad choices (i.e., if you $filter for underperformers in order to execute the "Fire()" operation you don't want the service to silently return your high performers as well.)
> Make $expand implicit if navigation properties are mentioned in $select or $aggregate
> -------------------------------------------------------------------------------------
>
> Key: ODATA-36
> URL: http://tools.oasis-open.org/issues/browse/ODATA-36
> Project: OASIS Open Data Protocol (OData) TC
> Issue Type: Improvement
> Components: OData Protocol v1.0, OData URL Conventions v1.0
> Affects Versions: WD01
> Environment: [Proposed]
> Reporter: Martin Zurmuehl
> Priority: Minor
> Fix For: WD01
>
>
> Currently clients need to repeat themselves when projecting on expanded entities:
> GET http://services.odata.org/OData/OData.svc/Products?$select=*,Category/Name&$expand=Category
> This could be reduced to
> GET http://services.odata.org/OData/OData.svc/Products?$select=*,Category/Name
> because the client explicitly requests Category/Name, and the server can only satisfy that if it expands the Category.
--
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
