Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

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

updated URL #2279

Merged
merged 2 commits into from
Dec 31, 2021
Merged

updated URL #2279

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
393f55a
updated URL
tiagov8 Dec 21, 2021
ff8b7cf
✅re-run workflow
JackDevAU Dec 24, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 7 additions & 3 deletions rules/do-pagination-server-side/rule.md → rules/do-pagination-database-side/rule.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,14 +1,18 @@
---
type: rule
title: Do you do pagination database side?
uri: do-pagination-server-side
uri: do-pagination-database-side
authors:
- title: Bryden Oliver
url: https://www.ssw.com.au/people/bryden-oliver
created: 2021-12-13T17:19:34.260Z
guid: ef94f559-ea04-4c00-8b27-f8f7b80f07f4
redirects:
- do-pagination-server-side

---
Pagination can be expensive if all the pages are retrieved from the database before grabbing the relevant page. It's much more efficient to get only the page number requested back from the database.

Pagination can be expensive if all the pages are retrieved from the database before grabbing the relevant page. It's much more efficient to get only the page number requested back from the database.

<!--endintro-->

Expand Down Expand Up @@ -47,4 +51,4 @@ return (count, result);

::: good
Figure: Good example - Reads only the count and 1 page of data from the database
:::
:::