Database API does not support pagination
Bug #1658710 reported by
Ian Cordasco
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| craton |
Fix Released
|
High
|
Ian Cordasco | ||
Bug Description
In order to support REST API pagination the database API needs to support passing around pagination information.
| Changed in craton: | |
| assignee: | nobody → Ian Cordasco (icordasc) |
| importance: | Undecided → High |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to craton (master) | #1 |
| Changed in craton: | |
| status: | In Progress → Fix Released |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit aad5fd33c3577a6
Author: Ian Cordasco <email address hidden>
Date: Mon Jan 23 08:56:45 2017 -0600
Update dbapi to perform pagination
This takes the first step towards performing and allowing pagination in
Craton's API. It prepared the database APIs to receive the pagination
parameters required to use oslo_db's paginate_query logic.
This also fixes an inconsistency in the /v1/users and /v1/projects calls
where {users,
but were in fact returning lists. These also need pagination applied, so
we have refactored them slightly and added pagination parameters to
those dbapi calls.
Closes-bug: #1658710
Partially-
Change-Id: I229de802e8ac35