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-622) Allow comparison of geo types, binary to null.


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

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

    Environment: [Proposed][Applied]  (was: [Proposed])

> 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 prohibit the use of eq, ne with binary and geo values, as these values are typically not comparable.
> However, 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, a strict reading of the current verbiage could be interpreted to mean that this disallows the common and useful case of comparing binary and geo values to null.



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


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