Why use returned instance after save() on Spring Data JPA Repository?

by

The save(…) method of the CrudRepository interface is supposed to abstract simply storing an entity no matter what state it is in. Thus it must not expose the actual store specific implementation, even if (as in the JPA) case the store differentiates between new entities to be stored and existing ones to be updated. That’s why the method is actually called save(…) not create(…) or update(…). We return a result from that method to actually allow the store implementation to return a completely different instance as JPA potentially does when merge(…) gets invoked.

Also, persistence implementations actually capable of dealing with immutable objects (i.e. not JPA) might have to return a fresh instance if the actual implementation requires populating an identifier or the like. I.e. it’s generally wrong to assume that the implementation would just consume the entity state.

So generally it’s more of an API decision to be lenient (permissible, tolerant) regarding the actual implementation and thus implementing the method for JPA as we do. There’s no additional proxy massaging done to the entities passed.

More Related Contents:

  1. setMaxResults for Spring-Data-JPA annotation?
  2. Using generics in Spring Data JPA repositories
  3. What is difference between CrudRepository and JpaRepository interfaces in Spring Data JPA?
  4. Handling soft-deletes with Spring JPA
  5. Spring CrudRepository findByInventoryIds(List inventoryIdList) – equivalent to IN clause
  6. Spring-Data FETCH JOIN with Paging is not working
  7. How to use @Transactional with Spring Data?
  8. Spring Data JPA: query ManyToMany
  9. Spring Data JPA find by embedded object property
  10. How to enable LockModeType.PESSIMISTIC_WRITE when looking up entities with Spring Data JPA?
  11. Spring Data + JPA with multiple datasources but only one set of Repositories
  12. Dynamic spring data jpa repository query with arbitrary AND clauses
  13. What is this spring.jpa.open-in-view=true property in Spring Boot?
  14. Spring Boot, Spring Data JPA with multiple DataSources
  15. Spring Data JPA – ZonedDateTime format for json serialization
  16. How to fetch FetchType.LAZY associations with JPA and Hibernate in a Spring Controller
  17. Spring-Data-Jpa Repository – Underscore on Entity Column Name
  18. Implementing custom methods of Spring Data repository and exposing them through REST
  19. Spring JpaRepository – Detach and Attach entity
  20. Use abstract super class as parameter for Spring data repository
  21. Are you supposed to have one repository per table in JPA?
  22. How to map sql native query result into DTO in spring jpa repository?
  23. Spring-boot: required a bean named ‘entityManagerFactory’ that could not be found
  24. Delete Not Working with JpaRepository
  25. Spring Data JPA: Query by Example?
  26. java.lang.NoSuchMethodError: javax.persistence.spi.PersistenceUnitInfo.getValidationMode()Ljavax/persistence/ValidationMode;
  27. How to store @Query sql in external file for CrudRepository?
  28. Missing CrudRepository#findOne method
  29. FetchMode join makes no difference for ManyToMany relations in spring JPA repositories
  30. Spring Data JPA – Is it possible to sort on a calculated property?

Leave a Comment