JpaRepository caches newly created object. How to refresh it?

by

If you are using Hibernate, this is the expected result. When you call translationRepository.saveAndFlush(translation) and translationRepository.findOne(t.getId()) one after the other, they hit the same Hibernate session which maintains a cache of all objects that it has worked on. Therefore, the second call simply returns the object passed to the first. There is nothing in those two lines that would have forced Hibernate to fire a SELECT query on the database for the Version entity.

Now, the JPA spec does have a refresh method on the EntityManager interface. Unfortunately, Spring Data JPA does not expose this method using its JpaRepository interface. If this method was available, you could have done t = translationRepository.saveAndFlush(translation) and then versionRepository.refresh(t.getVersion()) to force the JPA provider to synchronize the version entity with the database.

Implementing this method is not difficult. Just extend SimpleJpaRepository class from Spring Data JPA and implement the method yourself. For details see adding custom behaviour to all Spring Data JPA repositories.

An alternate would be to load the version entity as versionRepository.findOne(version.getId()) before setting it on the translation. Since you can hard-code version id in your code, your versions seem to be static. You can therefore mark your Version entity as @Immutable and @Cacheable (the former is a Hibernate-specific annotation). That way, versionRepository.findOne(version.getId()) should not hit the database every time it is called.

More Related Contents:

  1. How to properly use findBySomeOtherId not findById in Spring data jpa?
  2. Spring JPA selecting specific columns
  3. setMaxResults for Spring-Data-JPA annotation?
  4. Spring Data JPA – ZonedDateTime format for json serialization
  5. How does the FetchMode work in Spring Data JPA
  6. Spring-Data-Jpa Repository – Underscore on Entity Column Name
  7. Spring Data JPA – “No Property Found for Type” Exception
  8. Handling soft-deletes with Spring JPA
  9. How do I update an entity using spring-data-jpa?
  10. ImprovedNamingStrategy no longer working in Hibernate 5
  11. Spring CrudRepository findByInventoryIds(List inventoryIdList) – equivalent to IN clause
  12. Spring data jpa- No bean named ‘entityManagerFactory’ is defined; Injection of autowired dependencies failed
  13. Can I combine a @Query definition with a Specification in a Spring Data JPA repository method?
  14. JPA: update only specific fields
  15. Spring-Data FETCH JOIN with Paging is not working
  16. Refresh and fetch an entity after save (JPA/Spring Data/Hibernate)
  17. Why use returned instance after save() on Spring Data JPA Repository?
  18. Spring JpaRepository – Detach and Attach entity
  19. Use abstract super class as parameter for Spring data repository
  20. How to use @Transactional with Spring Data?
  21. Are you supposed to have one repository per table in JPA?
  22. Spring-boot: required a bean named ‘entityManagerFactory’ that could not be found
  23. Difference between save and saveAndFlush in Spring data jpa
  24. Delete Not Working with JpaRepository
  25. %Like% Query in spring JpaRepository
  26. spring data jpa @query and pageable
  27. JPQL Like Case Insensitive
  28. Spring Data JPA: query ManyToMany
  29. Spring Data JPA find by embedded object property
  30. Why has javax.persistence-api been replaced by jakarta.persistence-api in spring data jpa starter?

Leave a Comment