ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Databases & messaging · #hibernate
Developers want to measure the time spent executing the paginated Hibernate query separately from any post‑processing work (e.g., JSON serialization) that occurs after the query returns in a Dropwizard resource method annotated with @UnitOfWork. The @Timed annotation currently wraps the entire method, so the recorded metric conflates database fetch time with
Goal Determine the safest way to restore consistency of a Hibernate second‑level cache after a failed upgrade that leaves the database schema mismatched, while avoiding transient stale reads during recovery. Constraints and uncertainties Cache region uses read‑write or nonstrict‑read‑write strategy. Automatic expiry timeouts may delay consistency recovery. E
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
I don't see the "hibernation after X minutes" option in my Windows 11. On other computers I had, there was an option in Control Pane > Power Options > Change plan settings > Change advanced power settings . There i could set the time after which the computer should go into hibernation. Note that: I have hibernation enabled and can see it in the Star
Db2 LUW Global Temporary Table Memory Leak During Hibernate Pagination The Db2 LUW global temporary table (GTT) scope, defined as statement or transaction, is intended to release memory after statement completion, yet Hibernate's JOIN FETCH pagination may retain rows beyond the expected cleanup window. When large result sets are processed with setFirstResult
When managing large datasets in Hibernate, the setFirstResult and setMaxResults methods are used to bound queries and implement pagination by translating these calls into dialect-specific LIMIT and OFFSET clauses. A primary concern arises when navigating deep into a result set. As the start position increases, the database must scan and discard a growing num
In-Memory Pagination Behavior When utilizing setFirstResult() and setMaxResults() in Hibernate, the framework typically delegates pagination to the database using dialect-specific SQL clauses. However, a known behavior occurs when these methods are combined with join fetch on collection associations. In environments with small datasets, such as local develop
For a low-traffic application, enabling Hibernate's query cache with hibernate.cache.use_query_cache=true and @Cacheable can reduce database round-trips and connection occupancy. The cache stores result identifiers rather than entity state, and Hibernate invalidates those entries only when entity state changes through the ORM session lifecycle. When rows are
Goal: Verify that Hibernate’s setFirstResult and setMaxResults produce identical offset‑based pagination across PostgreSQL, MySQL, Oracle, and SQL Server when the query includes a non‑unique ORDER BY clause. Uncertainty: Different Hibernate releases may translate the same API call into dialect‑specific SQL differently, and some versions switch to in‑memory p
dropwizard
jule
xd
passport