Postgres allows you to create anonymous rows for use in queries. This is quite helpful when doing keyset pagination. The following SQL...
SELECT * FROM users
WHERE (userRank, id) > (10, 100)
is much nicer than...
SELECT * FROM users
WHERE userRank > 10
OR (userRank = 10 AND id > 100)
The already-existing Composite type comes close, but it requires that the composite be named, instead of just an anonymous row. Would there be interest in support for this functionality in this library? I could try to make a patch if so.
Postgres allows you to create anonymous rows for use in queries. This is quite helpful when doing keyset pagination. The following SQL...
is much nicer than...
The already-existing
Composite
type comes close, but it requires that the composite be named, instead of just an anonymous row. Would there be interest in support for this functionality in this library? I could try to make a patch if so.