[OASIS Issue Tracker] (ODATA-617) Allow eq/ne comparison of instances of same structured (complex or entity) type, allow eq/ne comparison with null for 0..1 nav props

From
OASIS Issues Tracker <>
Date
2016-03-03T13:26:50+00:00
ID
Thread
[OASIS Issue Tracker] (ODATA-617) Allow eq/ne comparison of instances of same structured (complex or entity) type, allow eq/ne comparison with null for 0..1 nav props
[ https://issues.oasis-open.org/browse/ODATA-617?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Pizzo updated ODATA-617:
--------------------------------

    Environment: [Proposed] Complex Types  (was: Complex Types)
       Proposal: 
can compare ordered collections: same members, same position
can compare unordered collections: same members, any order. don't expect this to work though...
can compare complex types by value (may fail if complex type contains unordered collection)
can compare two entities (as being the same reference)
  ex: Person(1)/BestFriend eq Person(2)/WorstEnemy
  ex: Person(1)/BestFriend eq {"@odata.id":"/People(1)"}
can compare entities to null:
  ex: Person(1)/BestFriend eq null

  was:See summary


> Allow eq/ne comparison of instances of same structured (complex or entity) type, allow eq/ne comparison with null for 0..1 nav props
> ------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: ODATA-617
>                 URL: https://issues.oasis-open.org/browse/ODATA-617
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData URL Conventions
>    Affects Versions: V4.0_OS
>         Environment: [Proposed] Complex Types
>            Reporter: Ralf Handl
>            Assignee: Ralf Handl
>              Labels: Usability
>             Fix For: V4.01_WD01
>
>
> These are natural extensions of the query language



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