ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
JHipster generates Spring Data JPA repositories that extend JpaRepository and expose server-side pagination via Pageable and Page. The frontend requests pages using page and size query parameters, and Hibernate translates the abstractions to database-specific LIMIT and OFFSET. The design goal is to understand the conditions under which paginated entity retri
Goal Implement pagination over a table with millions of rows while avoiding the performance degradation of OFFSET‑based queries and still integrating with Spring Data JPA repository methods. Constraints and uncertainty Hibernate 6 supports scrolling and custom SQL fragments that can express a seek‑method (WHERE id > :lastId ORDER BY id LIMIT :size), but t
Goal: Determine whether a Spring Data JPA repository method that returns an entity with a lazily loaded association should allow safe access to that association after the transaction ends without throwing an exception. Current behavior: Hibernate throws a LazyInitializationException when the association is accessed outside of an active transaction, unless fe
I'm designing a read endpoint over a table expected to hold tens of millions of rows, using Spring Data JPA (assume Spring Boot 3.x / Spring Data JPA 3.x). The API needs stable, bounded queries, but I'm torn between two documented approaches: returning Page<T> from a repository method with a Pageable , versus returning Slice<T> to skip the total-
I need to map two columns of entity class as json in postgres using spring data jpa. After reading multiple stackoverflow posts and baeldung post , How to map a map JSON column to Java Object with JPA https://www.baeldung.com/hibernate-persist-json-object I did configuration as below. However, I am facing error " ERROR: column "headers" is of type json but e
Asked · 05 Apr 2020, 00:11 UTC
answered · 09 Apr 2020, 19:23 UTC
hibernate
sema
spring
json
liquibase
jhipster