Paging library - Boundary callback for network + db with API taking page and size

Question

Short question:

What is the correct way to handle database + network on the Paging library from Architecture components, using an API that uses page + s

Answer 1

Lets say you always fetch N=10 items per page from the server & then store it in db. You can get the number of items in db using the sql query SELECT COUNT(*) FROM tbl & store it in variable count. Now to get the page number that should be requested next, use:

val nextPage: Int = (count / N) + 1