[
https://issues.apache.org/jira/browse/QPID-7165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15268692#comment-15268692
]
Keith Wall edited comment on QPID-7165 at 5/31/16 1:18 PM:
-----------------------------------------------------------
There is a defect in the order-by (and select) parsing when the input is in the
form {{a + b}}. It seems the parser fails, but the exception is not reported
(raised as separate JIRA QPID-7287)
was (Author: k-wall):
There is a defect in the order-by (and select) parsing when the input is in the
form {{a + b}}. It seems the parser fails, but the exception is not reported.
> Allow query results to be sorted and paginated
> ----------------------------------------------
>
> Key: QPID-7165
> URL: https://issues.apache.org/jira/browse/QPID-7165
> Project: Qpid
> Issue Type: New Feature
> Components: Java Broker
> Reporter: Keith Wall
> Fix For: qpid-java-6.1
>
> Attachments:
> 0001-QPID-7165-Java-Broker-Allow-query-results-to-be-sort.patch,
> 0001-QPID-7165-Java-Broker-Allow-query-results-to-be-sort.patch,
> 0002-QPID-7165-Java-Broker-Allow-query-results-to-be-sort.patch,
> 0002-QPID-7165-Java-Broker-Allow-query-results-to-be-sort.patch,
> 0004-WIP.patch
>
>
> Extend the mechanism provided by QPID-6969 to allow for the results set to be
> sorted by one or more columns and results set to be paginated.
> For the ordering clause, we could use SQL:2011 ORDER BY clause as a guide
> e.g. {{orderBy='x ASC,y DESC,z'}}
> For the pagination, SQL standardisation does not include it.
> https://en.wikipedia.org/wiki/Select_%28SQL%29#Result_limits We could opt for
> {{limit=}} {{offset=}} like MySQL/Sybase. We could also consider HTTP Range
> headers.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
