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-132) Support /$count in $select, $filter and $orderby


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

Ralf Handl updated ODATA-132:
-----------------------------

              Summary: Support /$count in $select, $filter and $orderby  (was: Support /$count in $filter and $orderby)
             Proposal: 
Support

    GET ~/Friends?$filter=Interests/$count gt 10&$orderby=Interests/$count 

for both collection properties and navigation properties.

Support

    GET ~/Friends?$expand=Interests&$select=*,Interests/$count

for both collection properties and navigation properties and use the same representation for the count in the inlined entity set as is used for representing the count of the base set in queries using $inlinecount=allpages.
          Environment: [Proposed]
          Component/s: OData Protocol v1.0
                       OData URL Conventions v1.0
        Fix Version/s: WD01
    Affects Version/s: WD01
          Description: 
ODATA-114 added suppport for /$count to collection valued properties.

This issue tracks supporting /$count in $select, $filter and $orderby. For example, we could support:

    GET ~/Friends?$filter=Interests/$count gt 10&$orderby=Interests/$count 

for either collection properties or navigations, or

    GET ~/Friends?$expand=Interests&$select=*,Interests/$count

The second example uses the same representation for the count in the inlined entity set as is used for representing the count of the base set in queries using $inlinecount=allpages.

  was:
ODATA-114 added suppport for /$count to collection valued properties.

This issue tracks supporting /$count in $filter and $orderby. For example, we could support:

    GET ~/Friends?$filter=Interests/$count gt 10&$orderby=Interests/$count 

for either collection properties or navigations. 


> Support /$count in $select, $filter and $orderby
> ------------------------------------------------
>
>                 Key: ODATA-132
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-132
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData ABNF Construction Rules v1.0, OData ATOM Format v1.0, OData JSON Format v1.0, OData Protocol v1.0, OData URL Conventions v1.0
>    Affects Versions: WD01
>         Environment: [Proposed]
>            Reporter: Michael Pizzo
>            Assignee: Michael Pizzo
>            Priority: Minor
>             Fix For: WD01
>
>
> ODATA-114 added suppport for /$count to collection valued properties.
> This issue tracks supporting /$count in $select, $filter and $orderby. For example, we could support:
>     GET ~/Friends?$filter=Interests/$count gt 10&$orderby=Interests/$count 
> for either collection properties or navigations, or
>     GET ~/Friends?$expand=Interests&$select=*,Interests/$count
> The second example uses the same representation for the count in the inlined entity set as is used for representing the count of the base set in queries using $inlinecount=allpages.

-- 
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]