[
https://issues.apache.org/jira/browse/CALCITE-4724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17397669#comment-17397669
]
Enze Liu commented on CALCITE-4724:
-----------------------------------
[~zabetak]
[https://clickhouse.tech/docs/en/sql-reference/statements/select/]
[https://clickhouse.tech/docs/en/sql-reference/table-functions/]
[https://clickhouse.tech/docs/en/sql-reference/statements/select/from/]
I think the select syntax and table function syntax can show that ClickHouse
does not support aliased values.
> ClickHouseSqlDialect `supportsAliasedValues` should return false.
> -----------------------------------------------------------------
>
> Key: CALCITE-4724
> URL: https://issues.apache.org/jira/browse/CALCITE-4724
> Project: Calcite
> Issue Type: Bug
> Components: core
> Affects Versions: 1.27.0
> Reporter: Enze Liu
> Priority: Minor
> Labels: pull-requests-available
>
> We use ClickHouseSqlDialect to do some sql optimize.
> for sql `select 1`, in the process of sqlNode -> relNode -> sqlNode, the sql
> string will be transformed to
> {code:java}
> SELECT *
> FROM (VALUES (1)) AS `t` (`EXPR$0`)
> {code}
> Since clickhouse is not support AliasedValues, all we need to do is to extend
> ClickHouseSqlDialect and make `supportsAliasedValues` return false.
> Maybe this kind of behavior can integrated into core?
> If needed, the pull request is ready.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
