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] Updated: (ODATA-339) $inlinecount and $count, do we need both? Could we use $count in select clause as well?

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

Ralf Handl updated ODATA-339:

    Environment: [Applied]  (was: [Resolved])

> $inlinecount and $count, do we need both? Could we use $count in select clause as well?
> ---------------------------------------------------------------------------------------
>                 Key: ODATA-339
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-339
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData ABNF Construction Rules, OData Protocol 
>    Affects Versions: V4.0_WD01
>         Environment: [Applied]
>            Reporter: Hubert Heijkers
>            Assignee: Ralf Handl
>             Fix For: V4.0_WD01
> In numerous cases one might want to just know, or also know, the count of the number of entities in a collection identified by a navigation property as opposed to retrieving the whole set. We allow already for $count to be appended to a resource path identifying a set. As of V4 we can now also nest the $inlinecount query option in the $expand to retrieve the count for that set after, also new, optionally applying a filter to that set. I can see cases were you would only want to retrieve the count without actually expanding such a navigation property. So I was wondering if we could allow the use of $count in a select to express the fact that the odata.count annotation for such navigation property ought to be included in the response and at the same time, while expanding, wouldn't want to use $count instead of $inlinecount in the expansion as well, thereby getting rid of the requirement for a special $inlinecount altogether.

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]