re: Pagination in an API: page number vs start index VIEW POST

re: Nice! I would say that's an upgraded version of number 2, as you're using something that can be indexed in the database rather than a usually gene...

For now I'd say it's not relevant because it's actually not dates but datetimes (including seconds), so most entities should have a unique datetime, so remainders after applying the limit are quite unlikely to happen. This API is still in early stages of development and is not fully tested so I might have missed some issues though 😅

Got it, so you could just use the datetime of the last one, and get the rest from there 👍

code of conduct - report abuse