[OASIS Issue Tracker] (ODATA-622) Allow comparison of geo types, binary to null.

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

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

Michael Pizzo updated ODATA-622:
--------------------------------

    Proposal: Explicitly state that binary, stream and geo values can only be compared to null using "eq null" and "ne null".  (was: Allow comparing binary and geo values to null using "eq null" and "ne null".)

> Allow comparison of geo types, binary to null.
> ----------------------------------------------
>
>                 Key: ODATA-622
>                 URL: https://issues.oasis-open.org/browse/ODATA-622
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData Protocol , OData URL Conventions 
>    Affects Versions: V4.0_OS
>         Environment: [Proposed][Applied]
>            Reporter: Michael Pizzo
>            Priority: Minor
>             Fix For: V4.0_ERRATA01
>
>
> We currently state that operators can be used with types other than geo, stream, and binary, as these values are typically not comparable, but we don't say what *can* be used with these types..
> It is valid to compare these values to null. This is handled in database systems, for example, by having "is null" and "is not null" operators, but since in OData we decided (after long debate) to use "eq null" and "ne null" to compare to null values (with appropriate null propagation rules). However, the current verbiage could be misinterpreted to mean that the common and useful case of comparing binary, stream and geo values to null is not supported.



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