JPA Updating Bidirectional Association

by

The question is should I apply merge on both sides as follows, and an I avoid the second merge with a cascade?

You can use the cascade annotation element to propagate the effect of an operation to associated entities. The cascade functionality is most typically used in parent-child relationships.

The merge operation is cascaded to entities referenced by relationships from Department if these relationships have been annotated with the cascade element value cascade=MERGE or cascade=ALL annotation.

Bidirectional relationships between managed entities will be persisted based on references held by the owning side (Employee) of the relationship. It is the developer’s responsibility to keep the in-memory references held on the owning side (Employee) and those held on the inverse side (Department) consistent with each other when they change. So, with below series of statements, the relationship will be synchronized to the database with a single merge:

Employee emp = new Employee();
Department dep = new Department();
emp.setDepartment(dep);
dep.getEmployees().add(emp);
...
entityManager.merge(dep);

These changes will be propagated to database at transaction commit. The in-memory state of the entities can be synchronized to the database at other times as well when a transaction is active by using the EntityManager#flush method.

More Related Contents:

  1. Hibernate throws MultipleBagFetchException – cannot simultaneously fetch multiple bags
  2. Hibernate Annotations – Which is better, field or property access?
  3. Hibernate JPA Sequence (non-Id)
  4. How to store date/time and timestamps in UTC time zone with JPA and Hibernate
  5. Bypass GeneratedValue in Hibernate (merge data not in db?)
  6. How does the FetchMode work in Spring Data JPA
  7. Hibernate – @ElementCollection – Strange delete/insert behavior
  8. JPA SQL Server No Dialect mapping for JDBC type: -9
  9. Transaction marked as rollback only: How do I find the cause
  10. JPA entity without id
  11. Can I combine a @Query definition with a Specification in a Spring Data JPA repository method?
  12. Multiple fetches with EAGER type in Hibernate with JPA
  13. Could not commit JPA transaction: Transaction marked as rollbackOnly
  14. Spring JpaRepository – Detach and Attach entity
  15. java.lang.IllegalStateException: Multiple representations of the same entity with @ManyToMany 3 entities
  16. JPA: what is the proper pattern for iterating over large result sets?
  17. JPA Query.getResultList() – use in a generic way
  18. @BatchSize a smart or stupid use?
  19. Spring Data JPA and Exists query
  20. Large Objects may not be used in auto-commit mode
  21. IllegalStateException with Hibernate 4 and ManyToOne cascading
  22. Force refresh of collection JPA entityManager
  23. Hibernate triggering constraint violations using orphanRemoval
  24. Error creating bean with name ‘entityManagerFactory
  25. JPA: How do I specify the table name corresponding to a class at runtime?
  26. Spring, JPA, and Hibernate – how to increment a counter without concurrency issues
  27. Why should anybody put annotations on the getters or setters when using JPA to map the classes?
  28. Hibernate using JPA (annotated Entities) and liquibase
  29. Change Table Name of an Entity on runtime? [duplicate]
  30. TransactionRequiredException Executing an update/delete query

Leave a Comment