Add getRecords with offset and limit, Add getRecordsCount(str) -> double #32
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When trying to retrieve a large number of large records, mono-wasm seems to choke on returns from IndexedDbManager.GetRecords. In my particular use case, it broke at around 300 records, and when I had 10000 records I needed to retrieve, this was a major blocker for me.
I have added two functions:
The parameter limit does what it says on the tin, limit the amount of records returned, and offset chooses how far to offset into the retrieved records before returning results. This version is an alternative to the regular GetRecords function, which remains as is.
This function provides a count of the number of records that are in a store without having to spend time serializing them to determine this. When dealing with a lot of records, using this paginated return to retrieve the results works, but is somewhat slow, and memory intensive when all I need is the count. This function alleviates this particular concern.
Tests of these new functions have been added to the test blazor page.