2.6 Persistence Operations (persist, find, merge, remove) (Week 2 • JPA & Hibernate)
1. Core Concept & Internal Working
Persistence Operations (persist, find, merge, remove) (JPA & Hibernate) covers `persist` (new entity), `find` vs `getReference` (lazy proxy), `merge` (returns managed copy!), and `remove`. In production software engineering, it is used to Using `em.getReference(Department.class, deptId)` to set a foreign key without firing an unnecessary `SELECT` on `departments`! Mastering its underlying execution rules and edge-case boundaries lets you write reliable, maintainable code.
2. Real-World Engineering Use Case
Using `em.getReference(Department.class, deptId)` to set a foreign key without firing an unnecessary `SELECT` on `departments`!
3. Granular Subtopics Covered
- `persist` (new entity): Core foundation of Persistence Operations (persist, find, merge, remove): Using `em.getReference(Department.class, deptId)` to set a foreign key without firing an unnecessary `SELECT` on `departments`!
- `find` vs `getReference` (lazy proxy): Master '`find` vs `getReference` (lazy proxy)' inside Persistence Operations (persist, find, merge, remove) across real-world inputs.
- `merge` (returns managed copy!): Master '`merge` (returns managed copy!)' inside Persistence Operations (persist, find, merge, remove) across real-world inputs.
- `remove`: Master '`remove`' inside Persistence Operations (persist, find, merge, remove) across real-world inputs.
- Production Pitfall Guard (Persistence Operations (persist, find, merge, remove)): Prevent common defect: Calling `em.merge(detached)` and continuing to mutate `detached` instead of the managed instance *returned* by `merge()`!
- Hands-On Verification (Persistence Operations (persist, find, merge, remove)): Implement `persist`, `find`, `getReference` FK linking, `merge`, and `remove` in an `EmployeeJpaRepository`.
4. Reference Implementation
Department deptRef = em.getReference(Department.class, deptId); // Zero SELECT needed just to set FK!
employee.assignDepartment(deptRef);
em.persist(employee);
5. Common Mistakes to Avoid
- Calling `em.merge(detached)` and continuing to mutate `detached` instead of the managed instance *returned* by `merge()`!
- Skipping boundary, null/empty, or error-state verification when implementing Persistence Operations (persist, find, merge, remove).
- Pushing untested Persistence Operations (persist, find, merge, remove) changes without clean naming and Git commit context.
6. Hands-On Exercise
Implement `persist`, `find`, `getReference` FK linking, `merge`, and `remove` in an `EmployeeJpaRepository`.
7. Technical Interview Checkpoints
- Q: What problem does Persistence Operations (persist, find, merge, remove) solve in JPA & Hibernate, and what fails if it is misused?
Key Focus: Using `em.getReference(Department.class, deptId)` to set a foreign key without firing an unnecessary `SELECT` on `departments`! Guard against: Calling `em.merge(detached)` and continuing to mutate `detached` instead of the managed instance *returned* by `merge()`! - Q: Explain the internal working of Persistence Operations (persist, find, merge, remove) (`persist` (new entity), `find` vs `getReference` (lazy proxy), `merge` (returns managed copy!), and `remove`).
Key Focus: Walk step-by-step through `persist` (new entity), `find` vs `getReference` (lazy proxy), `merge` (returns managed copy!), and `remove` with a concrete code example. - Q: How did you apply and verify Persistence Operations (persist, find, merge, remove) in your hands-on lab?
Key Focus: Implement `persist`, `find`, `getReference` FK linking, `merge`, and `remove` in an `EmployeeJpaRepository`.