In a traditional web application, when navigating to the next page, the application fetches records starting from the first record to the maximum records per page (e.g., if you're on page 10 with 50 records per page, it fetches all 500 records instead of just fetching records from 451 to 500).
My request table contains over 80K records, and when a user navigates to the last page, the application becomes unresponsive. Is there a solution to improve this?
Hi Mohammed,
We can achieve this only through an advanced query, and we also need to modify some properties in the table records and list navigation widget.
Refer to the attached solution. This approach worked for me in one of my projects, and it may be helpful for you as well.
This works for me Thank you
SELECT *
FROM your_table
ORDER BY some_column
OFFSET (number of rows to skip) ROWS FETCH NEXT (number of rows to fetch) ROWS ONLY;
Example, to fetch from row 500 to 550, the number of rows to skip will be 499 and to fetch the next 50 rows the value is 50, or the number of rows that you want to display.
Hope it helps you.