[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=64288#comment-64288 ] 

Ralf Handl commented on ODATA-1002:
-----------------------------------

Equality for ordered collections could be
 - same number of items
 - items at same index compare equal

For unordered collections it could be
 - same number of items
 - server enforces same order on both collections
 - items at same index compare equal

Note that ('Red','Green') would then differ from ('Red','Red','Green'), so equality of collections differs from equality of sets.

> 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.01_CSD02
>            Reporter: Hubert Heijkers
>
> 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)