ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
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
I am working with a Hibernate ORM 6 application backed by a relational database, and one entity table is expected to grow past 10 million rows. A reporting job must read every row once, while the UI only needs small pages of 20 records at a time. For the UI I currently use a TypedQuery with setFirstResult() and setMaxResults() , which the dialect translates
The goal is to stream a multi-million-row query in Hibernate ORM 6.x using ScrollableResults obtained from a StatelessSession , keeping heap usage flat while the JDBC driver batches rows according to a configured fetch size. The uncertainty sits at the Hibernate–JDBC boundary. Query#setFetchSize() and hibernate.jdbc.fetch_size are documented as hints, and dr
hibernate
gitter