[
https://issues.jboss.org/browse/TEIID-4316?page=com.atlassian.jira.plugin...
]
Ramesh Reddy edited comment on TEIID-4316 at 7/5/16 2:25 PM:
-------------------------------------------------------------
{code}
SELECT nullable_column FROM table_name WHERE nullable_column <> some_value
{code}
the "nullable_column" in where clause is different column than one in select ?
I tried same with postgres, I see the behavior as acceptable
{code}
test=# select * from customers;
id | name
----+-----------
1 | customer1
2 | customer2
3 | customer3
4 | customer4
5 |
(5 rows)
test=# select * from customers where name <> 'customer2'
test-# ;
id | name
----+-----------
1 | customer1
3 | customer3
4 | customer4
(3 rows)
{code}
was (Author: rareddy):
{code}
SELECT nullable_column FROM table_name WHERE nullable_column <> some_value
{code}
the "nullable_column" in where clause is different column than one in select ?
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)