[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (ODATA-576) Aggregation: Can we find a better way to represent nested expands?
[ http://tools.oasis-open.org/issues/browse/ODATA-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=36236#action_36236 ] Ralf Handl commented on ODATA-576: ---------------------------------- We could give expand() an optional third parameter that can be another expand transformation: GET ~/Categories?$apply=expand(Products,startswith(Name,'Ski'),expand(Sales,Amount gt 1000))/... Just expanding without filtering can be achieved by supplying true as the second parameter: GET ~/Categories?$apply=expand(Products,true,expand(Sales))/... This is closer to the new V4 $expand syntax: GET ~/Categories?$expand=Products($filter=startswith(Name,'Ski'),$expand=Sales($filter=Amount gt 1000))&... and GET ~/Categories?$expand=Products($expand=Sales)&... > Aggregation: Can we find a better way to represent nested expands? > ------------------------------------------------------------------ > > Key: ODATA-576 > URL: http://tools.oasis-open.org/issues/browse/ODATA-576 > Project: OASIS Open Data Protocol (OData) TC > Issue Type: Bug > Components: OData Extension for Data Aggregation > Affects Versions: V4.0_CSD01 > Reporter: Michael Pizzo > Fix For: V4.0_CSD02 > > > The current aggregation specification use the old path syntax for nested expands. This is inconsistent with the new way to represent expands in core. Can we figure out a syntax for nested expands in aggregation that is consistent with core? -- 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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]