ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Unbounded findAll() calls risk OOM as tables grow. Learn how Spring Data JPA Pageable bounds queries, why the default count query hurts, and when to switch to keyset pagination.
Learn how to replace Spring Data JPA’s Page with Slice to avoid costly count queries when paginating large datasets, and understand the trade‑offs involved.
A Spring Data JPA Page that returns too few rows usually means the COUNT query was never generated or was derived incorrectly. Diagnose it with SQL logging and fix it with explicit countQuery, Slice, or a custom fragment.
Learn how to implement custom paginated queries in Spring Data JPA using @Query and countQuery to ensure accurate total counts and prevent memory issues.
Context Spring Data JPA 6.x standardizes pagination through the Pageable and Sort interfaces, with PageRequest as the primary implementation. This abstraction delegates LIMIT / OFFSET generation to the underlying provider and supports dynamic ordering via Sort.by() without manual JPQL clauses. Constraint The Page return type requires a total count query, whi
When executing a native SQL query annotated with @Query in Spring Data JPA, passing a Pageable without an explicit LIMIT / OFFSET clause triggers an InvalidDataAccessApiUsageException . This indicates that pagination is unsupported for that query. The goal is to paginate large datasets efficiently while preventing accidental full result retrieval. Constraint
In a JHipster‑generated application the REST controllers expose CRUD endpoints that accept a Pageable object. The controller delegates to a Spring Data JPA repository and uses PaginationUtil to add X‑Total‑Count and Link headers. The framework accepts any pageSize value supplied by the client; the default is 20 but larger values are not capped. Because the g
JHipster scaffolds Spring Data JPA repositories and REST resources that expose list endpoints with Spring Data Pageable. The generated methods accept page, size and sort query parameters and return org.springframework.data.domain.Page, which is translated by JPA/Hibernate to LIMIT/OFFSET SQL. The goal is to bound queries over a large dataset and keep paginat
hibernate
spring
jhipster