OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


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


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

Ralf Handl edited comment on ODATA-897 at 1/21/16 11:03 AM:
------------------------------------------------------------

Inline count includes the total number of response records in a partial (paged) response. This already reflects $filter and $search applied to the requested collection.
 
Inlining a count that is produced by applying a different filter than the one used on the returned records seems odd.


was (Author: handl):
Inline count includes the total number of response records in a partial (paged) response. This already reflects $filter and $search applied to the requested collection.
 
Inlining a count that is produced by applying a different filter than the one used the returned records seems odd.

> 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?$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)


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]