[OASIS Issue Tracker] Updated: (ODATA-339) $inlinecount and $count, do we need both? Could we use $count in select clause as well?

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

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

Michael Pizzo updated ODATA-339:
--------------------------------

    Proposal: 
see also ODATA-323

- allowing /$count to be appended to any property representing a collection (of primitive, complex or entity type) in the $expand clause resulting in the count of the property being returned
-In Atom, support the metadata:count element as a direct child of a navigation link for getting just the count of related entities

  was:
see also ODATA-323

Use $count everywhere were the count of a collection is being referenced implying:
 - use of $count where currently $inlinecount is used
 - allowing /$count to be appended to any property representing a collection (of primitive, complex or entity type) in the $expand clause resulting in the count of the property being returned
-In Atom, support the metadata:count attribute as a direct child of a navigation link for getting just the count of related entities


> $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 
>         Environment: [Proposed]
>            Reporter: Hubert Heijkers
>
> 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