You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 21, 2022. It is now read-only.
For tables with a lot of entries it would be important to support "lazy loading", i.e. to allow fetching only the subset (offset, amount) of entries from the backend that is currently being displayed. This reduces the load on the backend (smaller query results) and results in smaller data transfers as most of the time e.g., the historic data (old reservations) are not required.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
For tables with a lot of entries it would be important to support "lazy loading", i.e. to allow fetching only the subset (offset, amount) of entries from the backend that is currently being displayed. This reduces the load on the backend (smaller query results) and results in smaller data transfers as most of the time e.g., the historic data (old reservations) are not required.
The text was updated successfully, but these errors were encountered: