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

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

I would overload "in" to mean "loperand is subset of roperand".

"intersects" would be a different operator:

  ('Red','Green') in ('Red','Green','Blue') --> true
  ('Red','Green') in ('Green','Blue') --> false
  ('Red','Green') intersects ('Green','Blue') --> true

@Hubert: The ABNF already allows JSON-style collections in URL expressions:

  Color in ["Red","Green","Blue"]

We just don't mention this explicitly in the section on the "in" operator. The overload with both operands collection-valued would then also accept

  ["Red","Green"] in ["Red","Green","Blue"]

Note the different quotes for strings.

> 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: ABNF Construction Rules, Protocol, URL Conventions
>    Affects Versions: V4.0_ERRATA03
>            Reporter: Hubert Heijkers
>            Assignee: 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)