[
https://issues.apache.org/jira/browse/CALCITE-6480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17866652#comment-17866652
]
Julian Hyde commented on CALCITE-6480:
--------------------------------------
Yes, Oracle traditionally treated BOOLEAN differently from other data types
(e.g. wouldn’t allow booleans in the SELECT clause) and you’d traditionally use
DECODE rather than CASE.
I gather that recent versions of Oracle support BOOLEAN, so the functionality
you are proposing should be turned off if Oracle is above a particular version.
> 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)
