[OASIS Issue Tracker] Updated: (ODATA-501) has operator is missing from the operator precedence table

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

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

Michael Pizzo updated ODATA-501:
--------------------------------

    Environment: [Proposed]
    Description: 
Section 5.1.1.9 defines operator precedence but doesn't mention the new "has" operator that can be used to determine if an enumeration value contains a particular member.

Enums only support equality and comparison operators, so it probably doesn't make a lot of difference.

If we add it to Primary then::

    Not style has Sales.Pattern'Yellow'

would be interpreted the same as::

   Not (style has Sales.Pattern'Yellow')


  was:
Section 5.1.1.9 defines operator precedence but doesn't mention the new "has" operator that can be used to determine if an enumeration value contains a particular member.

Enums only support equality and comparison operators, so it probably doesn't make a lot of difference, but I think I would tend to put "has" in with the unary operators.

       Proposal: Add "has" operator to the "Primary" group for operator precedence.

> has operator is missing from the operator precedence table
> ----------------------------------------------------------
>
>                 Key: ODATA-501
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-501
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData URL Conventions 
>    Affects Versions: V4.0_CS
>         Environment: [Proposed]
>            Reporter: Michael Pizzo
>             Fix For: V4.0_ERRATA01
>
>
> Section 5.1.1.9 defines operator precedence but doesn't mention the new "has" operator that can be used to determine if an enumeration value contains a particular member.
> Enums only support equality and comparison operators, so it probably doesn't make a lot of difference.
> If we add it to Primary then::
>     Not style has Sales.Pattern'Yellow'
> would be interpreted the same as::
>    Not (style has Sales.Pattern'Yellow')

-- 
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