Make sure AbstractEntity sets isNew flag in @PrePersist #269
Assignees
Milestone
Comments
odrotbohm
added a commit
that referenced
this issue
Jul 10, 2019
…ostPersist. This is to make sure that the persistence provider actually flips the flag in CrudRepository.save(…) or EntityManager.persist(…) to be precise. With the previous implementation the entity was returned from CrudRepository.save(…) as new which is wrong in itself but also caused test errors trying immediate subsequent deletions that run into an early return due to optimizations introduced for DATAJPA-1535.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
AbstractEntityis setting the transientisNewflag in an@PostPersistmethod. The invocation of that method can be delayed until actual database interaction by the JPA provider which might result in an entity instance being returned as new from a call toCrudRepository.save(…).We should move to tweaking the flag in
@PrePersist.The text was updated successfully, but these errors were encountered: