[jira] [Resolved] (OLINGO-836) Null compare handling when using eclipselink+oracle

["Michael Bolz (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/OLINGO-836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Bolz resolved OLINGO-836.
---------------------------------
    Resolution: Fixed

Hi [~tothgya],

Thanks for the contribution. 
The fix was [commited|https://git1-us-west.apache.org/repos/asf?p=olingo-odata2.git;a=commit;h=27fced0c26f84852df17d3cd343c0eb7642c95e6] and should be in the next release.

Kind Regards,
Michael

> Null compare handling when using eclipselink+oracle
> ---------------------------------------------------
>
>                 Key: OLINGO-836
>                 URL: https://issues.apache.org/jira/browse/OLINGO-836
>             Project: Olingo
>          Issue Type: Bug
>          Components: odata2-jpa
>    Affects Versions: V2 2.0.5
>            Reporter: Gyula Árpád Tóth
>            Assignee: Michael Bolz
>            Priority: Minor
>             Fix For: V2 2.0.7
>
>         Attachments: 0001-OLINGO-836-compare-to-null-handling.patch
>
>
> In ODataV2 null compares are done like this:
> property eq null
> Olingo v2 translates this to property = null which is fine if the database accepts these null compares or the JPA implementation's 'dialect' can take care of it.
> However JPA accepts the property is null expressions and that is handled correctly in eclipselink with oracle.
> The property = null expressions are failing with this combination.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)