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

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

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

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

    Description: 
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)

  was:
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.

Using JSON collections and a new "in" operator

    CountryCode in ["US","CA","DE"]

Allowing arbitrary collection expressions on the left side of lambda expressions

    ["US","CA","DE"]/any(c:c eq CountryCode)



> Add "in" operator as syntactic sugar for a chain of "or" expressions
> --------------------------------------------------------------------
>
>                 Key: ODATA-556
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-556
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData URL Conventions 
>    Affects Versions: V4.0_CSD03
>            Reporter: Ralf Handl
>             Fix For: V4.1_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 is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira