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 model-records/index route currently uses
findAllto 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 attributesoffsetandtotalto provide a paginated view of records.Perhaps this approach has already been considered but I couldn't find anything searching issues.