intermediateThe Persistence Context — First-Level Cache, Dirty Checking & Flush
Why does mutating a managed entity's field get persisted even without calling save() or update()?
Hibernate's dirty checking compares a managed entity's current field values against a snapshot taken when it was loaded, at flush time. If any field differs, Hibernate generates an UPDATE for it automatically — the entity is already tracked ('managed') by the persistence context, so no explicit save call is needed to trigger persistence.
Ready to master this question?
Generate a complete walkthrough — background, the full answer in plain language, a working code example explained line by line, a real-world scenario, common mistakes, and how this same question gets asked in different ways.
Sign in to generate a response