[
https://issues.apache.org/jira/browse/CALCITE-6480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17866744#comment-17866744
]
xiong duan commented on CALCITE-6480:
-------------------------------------
[~suibianwanwan33] What do you mean we need to parse TRUE to 1=1, FALSE =>1=0?
If the SQL is:
{code:java}
select * from table where true [false]{code}
The Calcite will optimize it. And `select 1=1` is invalid in Oracle. Others I
think we directly use 1 or 0. Did I miss something? Maybe we can use SQL to
illustrate it.
> OracleDialect does not support CASE WHEN returning boolean
> ----------------------------------------------------------
>
> Key: CALCITE-6480
> URL: https://issues.apache.org/jira/browse/CALCITE-6480
> Project: Calcite
> Issue Type: Wish
> Components: core
> Reporter: kate
> Priority: Minor
>
> Our requirement is to use Calcite to translate queries into different
> dialects. During validation in the TPC-DS scenario, we found that {{Oracle}}
> does not support SQL statements like
> {code:java}
> SELECT * FROM xxx
> WHERE CASE WHEN a > 10 THEN b < 5 ELSE c > 0 END;{code}
> Therefore, we hope to remove such predicates at the dialect like Oracle.
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
