[
https://issues.apache.org/jira/browse/PHOENIX-1768?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14376984#comment-14376984
]
Serhiy Bilousov commented on PHOENIX-1768:
------------------------------------------
That was easy one :)
[~jamestaylor] Would you able to comment on [comment
above|https://issues.apache.org/jira/browse/PHOENIX-1768?focusedCommentId=14375319&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14375319]
so I can have some clarity as of how to proceed in future and have some idea
what is the vision here, what to expect and what not to ... The least I am
interested in is to file JIRA(s) that will be just waste of everybody's time.
Thank you
> GROUP BY should support column position as well as column alias
> ---------------------------------------------------------------
>
> Key: PHOENIX-1768
> URL: https://issues.apache.org/jira/browse/PHOENIX-1768
> Project: Phoenix
> Issue Type: Bug
> Reporter: Serhiy Bilousov
>
> In postgreSQL (and many others DBs) you can specify not only column name for
> the GROUP BY but column number (position in SELECT part) as well as column
> alias.
> see:
> http://www.postgresql.org/docs/9.4/static/queries-order.html
> http://www.postgresql.org/docs/9.4/static/sql-select.html#SQL-GROUPBY
> Adding such support would be very helpful and sometimes necessary.
> I can provide real queries example if required but basically we want
> something like this
> given query
> SELECT a, b, TRUNC(current_date(),'HOUR') AS date_truncated FROM table
> we want
> GROUP BY 1, 2
> Having just column number would cover both but having column alias would make
> queries more readable and human friendly. Plus make it one little stem closer
> to postgreSQL and SQL standard.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
