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
The model-records/index route currently uses findAll to load all records of a given type. For adapters and backends that have non-trivial amounts of data, it is not practical to load all records on a single page.
Instead of using findAll, an alternate implementation could use query (with an empty query by default) and use the metadata attributes offset and total to provide a paginated view of records.
Perhaps this approach has already been considered but I couldn't find anything searching issues.
The text was updated successfully, but these errors were encountered:
The model-records/index route currently uses
findAll
to load all records of a given type. For adapters and backends that have non-trivial amounts of data, it is not practical to load all records on a single page.Instead of using
findAll
, an alternate implementation could usequery
(with an empty query by default) and use the metadata attributesoffset
andtotal
to provide a paginated view of records.Perhaps this approach has already been considered but I couldn't find anything searching issues.
The text was updated successfully, but these errors were encountered: