[
https://issues.apache.org/jira/browse/CALCITE-3986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17104084#comment-17104084
]
Julian Hyde commented on CALCITE-3986:
--------------------------------------
I don't know what you mean by "more verbose". The aliases are present in the
internal form (although I don't think they are added to the AST) but I thought
SqlImplementor could omit them when converting AST to SQL.
> Provide config option to omit assigning an alias that is identical to its
> identifier.
> -------------------------------------------------------------------------------------
>
> Key: CALCITE-3986
> URL: https://issues.apache.org/jira/browse/CALCITE-3986
> Project: Calcite
> Issue Type: Improvement
> Reporter: Drew Schmitt
> Priority: Minor
>
> The current alias assignment logic with the SqlValidator config option
> identifierExpansion() set to true will eagerly try to choose an alias, even
> if the alias name ends up being the same as the identifier itself. For
> example, it will assign the alias "foo" for the table "foo".
> It's nice to have alias assignment, but making it identical to the identifier
> doesn't always provide a whole lot of value and can make queries more verbose
> than they need to be.
> Suggest we add another SqlValidator config option (defaulted to the current
> behavior) to allow a caller to disable alias assignment in the cases that it
> would be identical to the identifier.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
