You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Julian Hyde (JIRA)" <ji...@apache.org> on 2017/01/25 21:44:26 UTC

[jira] [Resolved] (CALCITE-1535) Give error if ORDER BY clause references ambiguous column name

     [ https://issues.apache.org/jira/browse/CALCITE-1535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Julian Hyde resolved CALCITE-1535.
----------------------------------
       Resolution: Fixed
    Fix Version/s: 1.12.0

Fixed in http://git-wip-us.apache.org/repos/asf/calcite/commit/c3288a14. Thanks for the PR, [~zhenw]!

> 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
>             Fix For: 1.12.0
>
>
> 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)