`before` and `after` in the API skips over objects with identical `createdTime` about manifold HOT 4 OPEN

yeahh lol we really should do a real pagination method. for most APIs we can now, since we use supabase. the current behavior with before and after should stay the same though since it is semantically correct

I think this would be a pretty good task for an open source contribution ;)

from manifold.

change the query to SELECT * FROM BETS WHERE createdTime <= beforeId.createdTime && id != beforeId.id

Won't work if there are three bets A@1s, B@1s, C@1s and you've already got A and B; that solution would return A and C.

from manifold.

change the query to SELECT * FROM BETS WHERE createdTime <= beforeId.createdTime && id != beforeId.id

Won't work if there are three bets A@1s, B@1s, C@1s and you've already got A and B; that solution would return A and C.

Ah lol you're right - I guess you just need f64 timestamps eh

from manifold.

You can do something like:

SELECT *
FROM bets
WHERE
  (
    createdTime = beforeId.createdTime
    AND id < beforeId.id
  ) OR (
    createdTime < beforeId.createdTime
  )
ORDER BY
  createdTime DESC,
  id DESC

basically using the tuple (createdTime, id). With Postgres directly I think you could actually go even simpler:

SELECT *
FROM bets
WHERE
  (createdTime, id) < (beforeId.createdTime, beforeId.id)
ORDER BY
  createdTime DESC,
  id DESC

though that’s not supported via the public Supabase API.

from manifold.