[
https://issues.jboss.org/browse/TEIID-4316?page=com.atlassian.jira.plugin...
]
Steven Hawkins resolved TEIID-4316.
-----------------------------------
Resolution: Rejected
Almost all sources should support three-valued null logic. As Ramesh is showing with
Postgresql, a comparison with null will evaluate to unknown, which will not pass as true
in a where clause, thus no null rows.
Accumulo translator: null values not returned for <> criteria
in WHERE clause
-----------------------------------------------------------------------------
Key: TEIID-4316
URL:
https://issues.jboss.org/browse/TEIID-4316
Project: Teiid
Issue Type: Bug
Components: Misc. Connectors
Affects Versions: 8.12.5
Reporter: Jan Stastny
Assignee: Ramesh Reddy
For columns, which contain some null values, a query like:
{code:sql}
SELECT nullable_column FROM table_name WHERE nullable_column <> some_value
{code}
doesn't return null values.
Simple select works:
{code:sql}
SELECT nullable_column FROM table_name
{code}
returns all rows regardless whether they are null or not.
IS NULL criteria in WHERE clause also work:
{code:sql}
SELECT nullable_column FROM table_name WHERE nullable_column IS NULL
{code}
returns correct number of null values.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)