[
https://issues.apache.org/jira/browse/OLINGO-372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14263469#comment-14263469
]
dhaval gupta commented on OLINGO-372:
-------------------------------------
Hi,
Not null is applied with <> operator. But in oracle <> does not work with
null. If we want to write in oracle it should be like :
some attributes is not null and not <>.
Thanks
Dhaval.
> OData filter - Allow null Literals for binary operators
> -------------------------------------------------------
>
> Key: OLINGO-372
> URL: https://issues.apache.org/jira/browse/OLINGO-372
> Project: Olingo
> Issue Type: New Feature
> Components: odata2-core
> Affects Versions: V2 2.0.1
> Reporter: Sven Kobler-Morris
> Assignee: Sven Kobler-Morris
> Fix For: V2 2.0.1
>
>
> As defined in within the Specification [ms-odata]V2.pdf in chapter
> "2.2.3.6.1.1.5 Lifted Operators" the null literal should be allowed in
> $filter for negate,not,add,sub,mul,div,mod,gt,ge,lt,le,eq,ne,and,or
> operatores. But not for Member.
> The OData filter should not throw an exception if one of these operators is
> used with null ( e.g. "1 eq null"). The application must take care about the
> correct evaluation of null in thier context.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
