q-table server pagination limits without built-in query bounding

Direct answer

q-table does not enforce a maximum rowsPerPage when server is true. The pagination-change event is a notification, not a throttled command: Quasar does not debounce it, cancel earlier requests, or build limit/offset parameters. Validating page size, enforcing a maximum page size, constructing the remote payload, and managing loading and error states are entirely the application's responsibility.

Expected pagination contract

• The component emits pagination-change with page, rowsPerPage, sortBy, and descending. Exact property names can vary by Quasar major version.
• q-table does not fetch data. Your data layer reads page and rowsPerPage from the event and builds the API request.
• In server mode, set pagination.rowsNumber to the server-reported total record count after the response so the pager reflects the full dataset.

Likely explanation

Rapid pagination produces multiple pagination-change events before earlier responses arrive. Because the component does not own the HTTP layer, it cannot cancel in-flight requests or discard stale responses; that race must be handled in your data layer.

Steps for this case

1. Handle @pagination-change and extract event.page and event.rowsPerPage.
2. Clamp rowsPerPage to an allowed maximum, such as 100, before building the request; reject or normalize values outside that range.
3. Create one AbortController per page request and abort the previous controller when a new pagination-change arrives.
4. Apply only the response matching the latest request, then update rows and set pagination.rowsNumber to the server total.
5. Manage isLoading and error UI yourself; q-table does not set a loading state automatically in server mode.

Verification

• Log the pagination object inside @pagination-change and confirm it contains page, rowsPerPage, sortBy, and descending for your installed Quasar version.
• Select an unusually large rowsPerPage and confirm q-table does not reject it; your API layer must validate or truncate it.
• Trigger rapid page changes and confirm previous fetch promises are aborted and only the latest response updates the table.

Assumptions and uncertainty

This answer assumes standard Quasar q-table server-mode behavior. Property names and event timing are version-sensitive, so confirm them against your installed Quasar version before relying on them. Current verification against your specific version is required.

Missing diagnostic detail: which Quasar major version is installed? This determines the exact pagination property names and whether rowsNumber is the correct total-count property.