I'll take the blame for pushing you guys in this direction when I first had the issue with total (I I opened an issue with the postgres implementation). We've done more work around pagination and understanding how it works, we need this behavior fixed/amended within memory persistence for GetPageByFilter such that if I make a query for a given skip/take I'll get the same data and the total will represent the total amount of data represented to that query if I asked for all of it rather than a specific skip/take. This is assuming the underlying data doesn't change in a way to make the total change (this is expected and OK). Some examples are below:
If I perform a query that returns 100 items and I ask for a skip of 10 and a take of 10, I should get items 11-20 and the total should be 100
If I perform a query that returns 1000 items and I ask for a skip of 100 and a take of 1, I should get item 101 and the total should be 1000
Let me know if this makes sense, i'm going to copy+paste this same issue for data.
I'll take the blame for pushing you guys in this direction when I first had the issue with total (I I opened an issue with the postgres implementation). We've done more work around pagination and understanding how it works, we need this behavior fixed/amended within memory persistence for GetPageByFilter such that if I make a query for a given skip/take I'll get the same data and the total will represent the total amount of data represented to that query if I asked for all of it rather than a specific skip/take. This is assuming the underlying data doesn't change in a way to make the total change (this is expected and OK). Some examples are below:
Let me know if this makes sense, i'm going to copy+paste this same issue for data.