[OASIS Issue Tracker] (ODATA-1002) Add build in functions operating on collections of primitive (and complex?) types

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

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

Hubert Heijkers updated ODATA-1002:
-----------------------------------

    Proposal: 
Specify equality for collections of primitive types and extend the syntax, using the comma-separated list of literal primitive values enclosed by parens notation, to allow for comparison of arrays.
Equality for ordered collections would be defined as:
 - same number of items
 - all items in the array, at the same index, compare as equal
Equality for unordered collections would be defined as:
 - same number of items
 - all items in the array, after the server enforcing the same ordering on both collections, compare as equal, at the same index

Also extend the use of the "in" operator by allowing the left side to be a comma-separated list of literal primitive values enclosed by parens or an expression that resolves to a collection of the appropriate type. The operations would return true if the collections on the right hand side contains all the values contained in the list specified as the left hand side of the operator.

> Add build in functions operating on collections of primitive (and complex?) types
> ---------------------------------------------------------------------------------
>
>                 Key: ODATA-1002
>                 URL: https://issues.oasis-open.org/browse/ODATA-1002
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: New Feature
>          Components: OData ABNF Construction Rules, OData Protocol, OData URL Conventions
>    Affects Versions: V4.0_ERRATA03
>            Reporter: Hubert Heijkers
>              Labels: Proposed
>             Fix For: V4.01_CSD02
>
>
> I'm getting more asks for people wanting to filter against properties representing a collection of primitive type, most notably Collection(Edm.String).
> Things like equal to, not equal to and containing a value or subset are the operations that people are looking to do the most. The size of the array they can get around by using /$count.
> Short of coming up with something ourselves I was wondering if this is a more generic ask and if we could maybe guide implementations as to how to support this kind of functionality in a more generic way.  



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)