[
https://issues.apache.org/jira/browse/PHOENIX-3264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15504370#comment-15504370
]
Julian Hyde commented on PHOENIX-3264:
--------------------------------------
Yeah, you need to be in a particular environment (i.e. phase of statement
preparation) to use those things. That said, why not leave the constant as a
SqlLiteral, at least while it's in SqlOptionNode? The constructor of
SqlOptionNode is called from the parser, which is too early to have a validator
or sql-to-rel converter. But by the time you need the literal value, you'll
probably be in a validator anyway.
> Allow TRUE and FALSE to be used as literal constants
> ----------------------------------------------------
>
> Key: PHOENIX-3264
> URL: https://issues.apache.org/jira/browse/PHOENIX-3264
> Project: Phoenix
> Issue Type: Sub-task
> Reporter: James Taylor
> Attachments: SqlLiteral.png, SqlNodeToRexConverterImpl.png,
> SqlOptionNode.png, objectdependencies.png, objectdependencies2.png,
> stacktrace.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
(v6.3.4#6332)
