[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (ODATA-166) Inconsistent lifted operators for $filter
[ http://tools.oasis-open.org/issues/browse/ODATA-166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ralf Handl updated ODATA-166: ----------------------------- Environment: [Applied] (was: [Applying]) > Inconsistent lifted operators for $filter > ----------------------------------------- > > Key: ODATA-166 > URL: http://tools.oasis-open.org/issues/browse/ODATA-166 > Project: OASIS Open Data Protocol (OData) TC > Issue Type: Bug > Components: OData URL Conventions > Affects Versions: V4.0_WD01 > Environment: [Applied] > Reporter: Matthew Borges > Assignee: Ralf Handl > Priority: Minor > Fix For: V4.0_WD01 > > > I didn't see any mention of lifted operators in the working drafts. We should define how each operator behaves when one (or both) operands is null. > With that said, the V3 spec (section 2.2.3.6.1.1.5) is inconsistent with it's treatment of null: > - For equality operators, null eq null is true and null eq <anything not null> is false (i.e. the result is true or false) > - Any relational operators when compared with null are false (i.e. the result is true or false) > - This implies that null ge null and null le null is false which is inconsistent with null eq null is true > - Logical operators treat null as false (i.e. the result is true or false) > - Unary operators are null if the operand is null (i.e. in the case of not, the result is true, false, or null) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]