[
https://issues.apache.org/jira/browse/QPID-8104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16377128#comment-16377128
]
ASF subversion and git services commented on QPID-8104:
-------------------------------------------------------
Commit 7c69d1704b26064da9831a1c076fa0d3d43e6db8 in qpid-broker-j's branch
refs/heads/7.0.x from [~k-wall]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=7c69d17 ]
QPID-8104: [Broker-J] [Query] Generalise the implementation so that aliases may
appear within expressions within the order-by clause
(cherry picked from commit 38819bcac6dc5481357d2c05aaf281e7c83532fe)
> [Broker-J] [Query] [WMC] Ordering connections tables by port column fails
> with '422 - The orderBy expression at position '0' is unsupported'
> --------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: QPID-8104
> URL: https://issues.apache.org/jira/browse/QPID-8104
> Project: Qpid
> Issue Type: Bug
> Components: Broker-J
> Reporter: Keith Wall
> Priority: Minor
> Fix For: qpid-java-broker-7.0.2
>
>
> Ordering the connections table on the virtualhost tab by port ends with error
> {{422 - The orderBy expression at position '0' is unsupported}}.
> The select clause in question uses an alias {{port.name AS port}}. In
> general the ability to express an the order by in terms of column aliases is
> supported however, the issue here seems to be that {{port}} is ambiguous and
> could refer to the {{Collection#port}} attribute or the alias.
> The user of the query API can workaround by using a column number, or specify
> the column's expression rather than alias.
> I have not looked into this further.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
