[jira] [Commented] (QPID-7165) Allow query results to be sorted and paginated
[
https://issues.apache.org/jira/browse/QPID-7165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15263752#comment-15263752
]
ASF subversion and git services commented on QPID-7165:
---
Commit 1741584 from [~lorenz.quack] in branch 'java/trunk'
[ https://svn.apache.org/r1741584 ]
QPID-7165: [Java Broker] Fix opening query from VirtualHost tab and sort
visualisation in advanced mode
> 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
>Assignee: Lorenz Quack
> 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, QPID-7165-add-sorting-pagination.tar.gz
>
>
> 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: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7165) Allow query results to be sorted and paginated
[
https://issues.apache.org/jira/browse/QPID-7165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15262432#comment-15262432
]
ASF subversion and git services commented on QPID-7165:
---
Commit 1741469 from oru...@apache.org in branch 'java/trunk'
[ https://svn.apache.org/r1741469 ]
QPID-7165: [Java Broker] Allow query results to be sorted and paginated
> 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
>Assignee: Lorenz Quack
> 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, QPID-7165-add-sorting-pagination.tar.gz
>
>
> 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: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[jira] [Commented] (QPID-7165) Allow query results to be sorted and paginated
[
https://issues.apache.org/jira/browse/QPID-7165?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15220054#comment-15220054
]
Keith Wall commented on QPID-7165:
--
We want to check the relevant SQL standards concerning the syntax for the
sorting of a column that results from function/expressions and follow it if
possible.
For limit/offset, it seems there is not a broad consensus in the REST
implementing community regarding the correctness of the use of Range headers to
implement pagination. We said we would go we limit and offset query parameters
for now, and revisit the decision. Also when limit is returned the number of
records that would be returned if pagination were not in use must be returned
as part of the response.
> 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
>
>
> 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: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
