OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

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

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

Hubert Heijkers commented on ODATA-556:

Would it be safe to assume that with the added overload of 'contains' we didn't change it semantics in that it checks that the second parameter is a sub-string of any of the strings in the array passed as the first parameter correct? Also, it supposedly is it is safe to assume that one could pass property in the first parameter now that is of type Collection(Edm.String), correct?

> 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: New Query Capabilities
>            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"]
> or in a more URL-friendly notation (as double quotes and square brackets require percent-ending)
>     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

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]