Hibernate: without @Version, the last write silently wins

Two users load the same row, both edit different fields, both save. Hibernate issues two full UPDATEs and the second overwrites the first - no error, no conflict, and the first user's change is simply gone.

• Hibernate: getReference hands back a proxy that throws after the session closes
• Hibernate: orphanRemoval and CascadeType.REMOVE are different rules
• Hibernate: equals/hashCode on a generated id breaks HashSet membership
• Hibernate: the first-level cache means a re-query never sees another transaction's update
• Hibernate: merge returns a copy, and the object you passed in stays detached
• Hibernate: flush order is fixed, so a unique constraint fails on a swap

---

Run this yourself in the Online Java Compiler, spin up a live REST API in the API Sandbox, or practise with Java interview questions.

Published 2026-08-25

© Java Coding Hub · About · Contact · Privacy · Terms