UUID Cursor Pagination

Problem

If you have non-sequential UUID’s as your primary key, the take/cursor prisma pagination API doesn’t work. I believe it actually did with the old first/after/before/last API (could be wrong here but it seemed to prior to beta.7).

In such cases, you can paginate using a query similar to this:

SELECT * FROM events 
  WHERE (created,id) >= ($<after>,$<id>)
  ORDER BY created ASC ,id ASC LIMIT 10

Suggested solution

A cursor combining the uuid id field and a created_at field works when passed in as the cursor to prisma.

Alternatives

You can almost implement an equivalent query using just where/order by but it is not currently possible to pass multiple fields to orderBy.

Additional context

[gersomvg]

@dpetrick What’s the implication of the fix? Is it now that you can orderBy only a date and have an ID as cursor? Does it behind the scenes first sort on date and after that on id?

If so, the docs should also reflect this, since it mentions that you need to orderBy the cursor. Happy to make a docs PR.

[dpetrick]

A fix is available from 2.2.0-dev.19 onwards.