[OLINGO-836] Null compare handling when using eclipselink+oracle

• Type: Bug
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: V2 2.0.5
• Fix Version/s: V2 2.0.7
• Component/s: odata2-jpa
• Assignee: mibo
• Reporter: Gyula Árpád Tóth
• Created: 14/Dec/15 08:25
• Updated: 03/Mar/16 07:31
• Resolved: 03/Mar/16 07:30

Description

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.