We (and the SQL standard) don't allow raw NULLs. I'm not convinced that BOOLEAN should be treated differently from other types. The only difference between BOOLEAN and other types is that BOOLEAN allows UNKNOWN as a synonym for NULL; none of your examples use UNKNOWN.
On Tue, Dec 6, 2016 at 8:18 AM, Serhii Harnyk <[email protected]> wrote: > Hello, > > I have created pull request to CALCITE-1531 > <https://issues.apache.org/jira/browse/CALCITE-1531>: > https://github.com/apache/calcite/pull/335. > NULL in boolean operators in Calcite corresponds to Boolean type UNKNOWN, > so when NULL is used in this operators, we shouldn't throw exception and > continue query execution. > > Could anyone please review it? > > Kind regards, > Serhii Harnyk
