search: if limit === total, cursor should be null

[Dzieni]

Small bugfix, bug found by @chiss2906

[wmertens]

I'm wondering if we should change the API so you always get the cursor and an additional hasMore boolean. This allows paging through future results.

The API change could coincide with the API change I propose in #9 and the transact branch

[Dzieni]

@wmertens
Good point, but then it's going to be a breaking change, right? While adding hasMore is not breaking anything, we're going to change the behavior of cursor a bit. That means all of those 3 changes would make strato-db v4.

Should we make a v4 roadmap then?

[wmertens]

I created a next branch for v4. So we could implement hasMore on there.

But I think maybe we can avoid breakage by returning the cursor twice, in the field named e.g. lastCursor? That one will always have the cursor for the last element, and cursor will keep the same semantics. Or is that too ugly and is the breaking change easy to handle in application code?