[OASIS Issue Tracker] (ODATA-556) Add "in" operator as syntactic sugar for a chain of "or" expressions

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

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

Ralf Handl updated ODATA-556:
-----------------------------

    Environment: [Proposed]
       Proposal: See description 1)

> Add "in" operator as syntactic sugar for a chain of "or" expressions
> --------------------------------------------------------------------
>
>                 Key: ODATA-556
>                 URL: https://issues.oasis-open.org/browse/ODATA-556
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData URL Conventions
>    Affects Versions: V4.0_CSD03
>         Environment: [Proposed]
>            Reporter: Ralf Handl
>            Assignee: Ralf Handl
>              Labels: GoodIdea, Usability
>             Fix For: V4.01_WD01
>
>
> In data analysis it is common to retrieve data that matches one of several distinct values, reflected in SQL as the IN operator.
> This is syntactic sugar, so we need to balance between a convenient notation and adding value to the expression syntax that we already have.
> 1) Using JSON collections and a new "in" operator:
>     CountryCode in ["US","CA","DE"]
> 2) Allowing arbitrary collection expressions on the left side of lambda expressions:
>     ["US","CA","DE"]/any(c:c eq CountryCode)
> 3) Adding an overload to the contains function:
>     contains(["US","CA","DE"], CountryCode)



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