[OASIS Issue Tracker] (ODATA-897) Allow the count of a filtered/searched collection in common expressions

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

     [ https://issues.oasis-open.org/browse/ODATA-897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Pizzo updated ODATA-897:
--------------------------------

    Description: 
The count of a collection-valued (structural or navigation) property can already be used in common expressions, e.g. in $orderby. 

It would be useful to also allow the /$count segment followed by a nested filter or search option, e.g. 

GET entitySet?$filter=navigationProperty/$count($filter=YYY) gt 5&$expand=navigationProperty/$count($filter=XXX)&$orderby=navigationProperty/$count($filter=XXX) desc

to get the entities with the highest number of related entities matching filter first.

This was proposed on the Olingo mailing list: http://mail-archives.apache.org/mod_mbox/olingo-user/201512.mbox/%3C5662B48C.7020305%40gmail.com%3E

  was:
The count of a collection-valued (structural or navigation) property can already be used in common expressions, e.g. in $orderby. 

It would be useful to also allow the /$count segment followed by a nested filter or search option, e.g. 

GET entitySet?$expand=navigationProperty/$count($filter=XXX)&$orderby=navigationProperty/$count($filter=XXX) desc

to get the entities with the highest number of related entities matching filter first.

This was proposed on the Olingo mailing list: http://mail-archives.apache.org/mod_mbox/olingo-user/201512.mbox/%3C5662B48C.7020305%40gmail.com%3E


> Allow the count of a filtered/searched collection in common expressions
> -----------------------------------------------------------------------
>
>                 Key: ODATA-897
>                 URL: https://issues.oasis-open.org/browse/ODATA-897
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData URL Conventions
>    Affects Versions: V4.0_ERRATA02
>         Environment: New Query Capabilities; [Proposed]
>            Reporter: Ralf Handl
>             Fix For: V4.01_WD01
>
>
> The count of a collection-valued (structural or navigation) property can already be used in common expressions, e.g. in $orderby. 
> It would be useful to also allow the /$count segment followed by a nested filter or search option, e.g. 
> GET entitySet?$filter=navigationProperty/$count($filter=YYY) gt 5&$expand=navigationProperty/$count($filter=XXX)&$orderby=navigationProperty/$count($filter=XXX) desc
> to get the entities with the highest number of related entities matching filter first.
> This was proposed on the Olingo mailing list: http://mail-archives.apache.org/mod_mbox/olingo-user/201512.mbox/%3C5662B48C.7020305%40gmail.com%3E



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