We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We currently use "OFFSET"/"LIMIT" for pagination. It's simple and works great for our current data size.
As we get to larger data sets, it will start to incur some performance penalties.
The "right" way to implement pagination at scale is called "keyset" pagination: https://www.citusdata.com/blog/2016/03/30/five-ways-to-paginate/ https://leopard.in.ua/2014/10/11/postgresql-paginattion
This is supported/encouraged in the FHIR graphql spec: https://www.hl7.org/fhir/graphql.html#searching
(named "cursor", unrelated to a db cursor)
The text was updated successfully, but these errors were encountered:
No branches or pull requests
We currently use "OFFSET"/"LIMIT" for pagination. It's simple and works great for our current data size.
As we get to larger data sets, it will start to incur some performance penalties.
The "right" way to implement pagination at scale is called "keyset" pagination:
https://www.citusdata.com/blog/2016/03/30/five-ways-to-paginate/
https://leopard.in.ua/2014/10/11/postgresql-paginattion
This is supported/encouraged in the FHIR graphql spec:
https://www.hl7.org/fhir/graphql.html#searching
(named "cursor", unrelated to a db cursor)
The text was updated successfully, but these errors were encountered: