[
https://issues.apache.org/jira/browse/PHOENIX-1749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14485911#comment-14485911
]
Alicia Ying Shu edited comment on PHOENIX-1749 at 4/8/15 8:41 PM:
------------------------------------------------------------------
[~jamestaylor]I used a different way to do it, does the below make sense?
tableName =
TableName.create(context.getCurrentTable().getTable().getSchemaName().toString(),
context.getCurrentTable().getTable().getName().toString());
ColumnParseNode colParseNode = new ColumnParseNode(tableName,
colProj.getName(), null);
expression = colParseNode.accept(visitor);
My tests passed.
was (Author: aliciashu):
[~jamestaylor]I used a different way to do it, does the below make sense?
tableName =
TableName.create(context.getCurrentTable().getTable().getSchemaName().toString(),
context.getCurrentTable().getTable().getName().toString());
ColumnParseNode colParseNode = new ColumnParseNode(tableName,
colProj.getName(), null);
expression = colParseNode.accept(visitor);
> ORDER BY should support ordinal position as well as expression
> --------------------------------------------------------------
>
> Key: PHOENIX-1749
> URL: https://issues.apache.org/jira/browse/PHOENIX-1749
> Project: Phoenix
> Issue Type: Bug
> Reporter: Serhiy Bilousov
> Assignee: Alicia Ying Shu
> Attachments: PHOENIX-1749-v1.patch, PHOENIX-1749.patch
>
>
> In postgreSQL (and many others DBs) you can specify not only column name for
> the ORDER 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
> ORDER BY 1 ASC, 2 DESC
> ORDER BY date_truncated
> 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)
