When does Hibernate’s setFirstResult cause excessive row scanning that degrades pagination performance?
The goal is to identify the practical offset size at which Hibernate’s setFirstResult forces the database to scan rows up to the offset instead of using an index seek, and to evaluate how this performance penalty compares with cursor‑based pagination that uses a unique identifier from the last fetched row. Constraints include Hibernate version differences—na
nano