You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 30, 2022. It is now read-only.
Some of our paginated endpoints don't use a consistent ordering on the query sets they paginate. This means that the ordering can change between queries, and as such can lead to pagination where the same record is repeated on multiple pages. As per the Postgres spec (https://www.postgresql.org/docs/current/queries-order.html) if no sorting is explicitly chosen, rows will be returned in an unspecified order.
Affected Endpoints
/connection
/dataset
/policy
/storage/config
Expected Behaviour
Objects should be returned ordered by their .created_at field in descending order. ie. most recent objects first.
The text was updated successfully, but these errors were encountered:
Bug Description
Some of our paginated endpoints don't use a consistent ordering on the query sets they paginate. This means that the ordering can change between queries, and as such can lead to pagination where the same record is repeated on multiple pages. As per the Postgres spec (https://www.postgresql.org/docs/current/queries-order.html) if no sorting is explicitly chosen, rows will be returned in an unspecified order.
Affected Endpoints
/connection
/dataset
/policy
/storage/config
Expected Behaviour
.created_at
field in descending order. ie. most recent objects first.The text was updated successfully, but these errors were encountered: