No PDF cheat sheet teaches you that—because it is an architectural pattern, not a Hibernate property. Every "High-Performance Java Persistence" summary tells you to use JOIN FETCH carefully. They warn about Cartesian products.
// Slow: Fetches entire entities, forces dirty checking List<Post> posts = entityManager.createQuery("select p from Post p", Post.class).getResultList(); High-performance code does this: high-performance java persistence book pdf
The high-performance secret? Instead of updating item.current_price , you append a bid to a separate bid_history table and calculate the price on the fly via a materialized view. You bypass the lock entirely. No PDF cheat sheet teaches you that—because it