ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
When datasets grow, a Quasar QTable that renders every row in the browser becomes sluggish. This post shows how to use QTable’s request event to delegate slicing, sorting, and total counts to a backend API, keeping the client lean and responsive.
Quasar's QTable can hand paging, sorting, and filtering to your backend via the pagination prop and @request event. Here's the wiring, the rowsNumber gotcha, and the trade-offs.
Learn how to configure Quasar’s QTable for server‑side pagination and sorting, with loading indicators, error handling, and state persistence. Step‑by‑step guide with example code and validation tips.
Goal Implement server‑side pagination for a QTable that displays millions of rows. The table must support dynamic sorting and filtering while keeping the UI responsive. Constraints & Uncertainty Quasar’s @request event delivers a pagination object with page , rowsPerPage , sortBy , descending , and filter fields. Client‑side pagination requires the full
quasar