phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Eric Lomore (JIRA)" <>
Subject [jira] [Commented] (PHOENIX-3264) Allow TRUE and FALSE to be used as literal constants
Date Thu, 15 Sep 2016 23:15:21 GMT


Eric Lomore commented on PHOENIX-3264:

Thanks James that makes it very clear :)
[~julianhyde] you  mentioned using SqlNodeToRexConverterImpl to do the conversion.
On the calcite side, its constructor has no access identifier, and hence can't be accessed
by the phoenix package.
I have been unable to circumvent this through other means - do you have any thoughts or is
there something I am missing?

Thanks very much!

> Allow TRUE and FALSE to be used as literal constants
> ----------------------------------------------------
>                 Key: PHOENIX-3264
>                 URL:
>             Project: Phoenix
>          Issue Type: Sub-task
>            Reporter: James Taylor
>         Attachments: SqlLiteral.png, SqlNodeToRexConverterImpl.png, SqlOptionNode.png,
> Phoenix supports TRUE and FALSE as boolean literals, but perhaps Calcite doesn't? Looks
like this is leading to a fair number of failures.

This message was sent by Atlassian JIRA

View raw message