ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Hibernate ORM exposes setFirstResult() and setMaxResults() on Query and TypedQuery to paginate results, delegating to the configured dialect to emit LIMIT / OFFSET or ROWNUM clauses. When a query fetches a collection association, the framework may log HHH000104: firstResult/maxResults specified with collection fetch; applying in memory! and shift pagination
Paginating a fetch-joined collection without loading the full result set I have a JPA query (Hibernate 6.x, Spring Data JPA) that fetches a parent entity together with a collection-valued association using join fetch , and the repository method also applies pagination via setFirstResult / setMaxResults (through Pageable ). The goal is a page of parent entiti
When a Hibernate query uses a fetch join (e.g., left join fetch) together with pagination via setFirstResult and setMaxResults, the application expects each page to contain a exact number of distinct root entities. However, the LIMIT/OFFSET clause is applied to the joined result set before Hibernate removes duplicate rows, so the number of distinct entities
Goal: configure Hibernate so that a paginated HQL query with a fetch join returns the requested number of distinct root entities without manually adding DISTINCT to the query string. Constraint: Hibernate 5.x and 6.x do not inject an implicit DISTINCT when setFirstResult/setMaxResults are used together with a fetch join, causing duplicate SQL rows and potent
The goal is to retrieve a limited set of distinct parent entities (e.g., Authors) while eagerly fetching their child collections (e.g., Books) using a fetch join, without returning partial collections caused by the limit cutting off duplicate rows. The uncertainty lies in whether Hibernate automatically adds DISTINCT to collapse duplicates before applying se
Goal: obtain predictable pagination results for a JPQL/HQL query that uses fetch joins on a OneToMany association and includes an ORDER BY clause when upgrading from Hibernate 5.6 to 6.0 with the MySQL dialect. In Hibernate 5.6 the limit/offset is applied before distinct root‑entity filtering, which can cause duplicate root rows in the result set. Hibernate
Large‑Dataset Pagination with Fetch Joins When querying a parent entity that eagerly fetches a collection, Hibernate can materialize the same root multiple times before deduplication. This becomes problematic when paginating a very large result set: the setMaxResults method applies a LIMIT/OFFSET clause, but the offset may be applied after the join, causing
When paginating results with Hibernate’s Criteria API using setFirstResult and setMaxResults , the goal is to retrieve a stable, non‑overlapping slice of data across multiple executions. However, without an explicit ORDER BY clause the database may return rows in arbitrary physical order, and fetch joins on collection associations can produce duplicate root
towergit
hibernate