phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Geoffrey Jacoby (JIRA)" <j...@apache.org>
Subject [jira] [Created] (PHOENIX-5065) Inconsistent treatment of NULL and empty string
Date Fri, 07 Dec 2018 22:48:00 GMT
Geoffrey Jacoby created PHOENIX-5065:
----------------------------------------

             Summary: Inconsistent treatment of NULL and empty string
                 Key: PHOENIX-5065
                 URL: https://issues.apache.org/jira/browse/PHOENIX-5065
             Project: Phoenix
          Issue Type: Bug
    Affects Versions: 4.14.1
            Reporter: Geoffrey Jacoby


Phoenix doesn't handle NULLs consistently with other SQL dialects, and it doesn't handle them
consistently internally either. 

In PHOENIX-2422, [~jamestaylor] mentioned that Phoenix's intended behavior is for empty string
and NULL to be equivalent. That's inconsistent with other SQL dialects (in which NULL is never
equal to anything, including itself), but if that's our documented behavior, then that's fine
unless PHOENIX-2422 to change it is ever worked. 

But consider the following queries:

{code:java}
SELECT COUNT(*) FROM SYSTEM.CATALOG WHERE TENANT_ID = '';
-- Returns 0 rows
SELECT COUNT(*) FROM SYSTEM.CATALOG WHERE TENANT_ID IS NULL;
-- Returns some number of rows. Call it N
SELECT COUNT(*) FROM SYSTEM.CATALOG WHERE TENANT_ID IN ('');
-- Returns 0 rows
SELECT COUNT(*) FROM SYSTEM.CATALOG WHERE TENANT_ID IN ('', 'FOO');
-- Returns N rows. 
{code}






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message