[
https://issues.apache.org/jira/browse/CALCITE-1535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15833360#comment-15833360
]
zhen wang commented on CALCITE-1535:
------------------------------------
I'm good. not that familiar with sql spec.
it's just when are the two earlier unit tests supposed to be fixed?
if we treat 'explicit' alias the same as `implicit` alias, then feels the two
will never be fixed. or rather should they be fixed as comments suggests in the
first place.
> Give error if ORDER BY clause references ambiguous column name
> --------------------------------------------------------------
>
> Key: CALCITE-1535
> URL: https://issues.apache.org/jira/browse/CALCITE-1535
> Project: Calcite
> Issue Type: Improvement
> Affects Versions: 1.11.0
> Reporter: Dongming Liu
> Assignee: Julian Hyde
>
> When I use calcite, I found follow sql can convert to a RelNode correctly.
> {code}
> SELECT id AS t1, name AS t1 FROM T ORDER BY t1
> {code}
> The column name t1 for {{ORDER BY}} is ambiguous, should check at validation?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
