ScrollableResults fetch size on a Hibernate 6 StatelessSession: hint or guarantee?
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