[
https://issues.apache.org/jira/browse/CALCITE-1535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15734790#comment-15734790
]
Julian Hyde commented on CALCITE-1535:
--------------------------------------
It's OK for column aliases to be non-unique (for a top-level query) but if you
reference a non-unique column name in an ORDER BY clause I agree it should give
an error, say "Ambiguous column name 'T1' in ORDER BY".
> Validator does not check order by 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)
