[OASIS Issue Tracker] Created: (ODATA-393) Allow querying collections of primitive type instances similar to other collections

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

Allow querying collections of primitive type instances similar to other collections
-----------------------------------------------------------------------------------

                 Key: ODATA-393
                 URL: http://tools.oasis-open.org/issues/browse/ODATA-393
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Sub-task
          Components: OData ABNF Construction Rules, OData URL Conventions 
    Affects Versions: V4.0_CSD01
         Environment: [Proposed]
            Reporter: Ralf Handl
             Fix For: V4.0_CSD02


Collections of entities and complex type instances are now treated equally, but collections of primitive values are somewhat neglected. They do allow the path suffix /$count, and the query options $count, $top and $skip are straight-forward.

For $filter and $orderby we need one tiny generalization: we currently allow common expressions within the lambda operators any() and all() to use $it for addressing the current entity, and we can use that to filter collections of primitive values:

GET ~/Customers(1)/EmailAddresses?$filter=endswith($it,'.com')

This increased flexibility is also useful for querying collections of entities:

GET ~/Employees?$filter=$it eq Manager

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