[
https://issues.apache.org/jira/browse/CASSANDRA-5075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13649628#comment-13649628
]
Sylvain Lebresne commented on CASSANDRA-5075:
---------------------------------------------
I'd prefer separating the aliasing from the other RawSelector. We pretty much
always need to call getUnaliased() first to retrieve the "real" selector, so
having AliasedSelector and the other selector being of the same type feels
error prone for no advantages. Instead, I would typically rename the current
RawSelector interface to say "Selectable", and then make RawSelector be a pair
of a "Selectable" and a (potentially null) alias. Anecdotally this would also
avoid adding new methods to ColumnIdentifier which bugs me for some reason.
Nit: could be nice to throw a specific "aliases are not supported in <x>
clause" message if someone uses an alias in a WHERE or ORDER BY clause.
> CQL Add support for AS keyword in select
> ----------------------------------------
>
> Key: CASSANDRA-5075
> URL: https://issues.apache.org/jira/browse/CASSANDRA-5075
> Project: Cassandra
> Issue Type: Improvement
> Components: API
> Reporter: Alexandr Kulik
> Assignee: Aleksey Yeschenko
> Priority: Minor
> Fix For: 2.0
>
>
> It would be nice to have support of AS keyword in select statement. It would
> allow to use jpa frameworks without writing custom sql/cql's.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
