[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:comment-tabpanel&focusedCommentId=66244#comment-66244 ] 

Michael Pizzo commented on ODATA-1002:
--------------------------------------

In reviewing the application, two questions came up:
1) is [1,1,2] subsetof [1,2] ?  (do elements of the left operand have to occur at least as many times in the right operand)
2) is [3,1] subsetof [4,1,3]? (does order matter)

For #2, if the collections are unordered, then [3,1] subsetof [4,1,3] should be true, but what about for ordered collections?


> 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: URL Conventions
>    Affects Versions: V4.0_ERRATA03
>         Environment: Applied
>            Reporter: Hubert Heijkers
>            Assignee: Ralf Handl
>              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)