Jens Schauder
Jens Schauder
If you want to use the positive result of the `find` call as an indication that the entity in question is managed, you'd have to use `existing` as an argument...
Yes, but it won't throw an exception when the change happend before the `find`
Nobody said that `merge` gets called to avoid `OptimisticLockingFailureException`. The opposite is true. In the situation described in my first comment we must have an `OptimisticLockingFailureException`!
Yes, when `entity` is in detached state. `find` will return a different instance and `entity` is still detached, i.e. `contains(entity)` will return `false`.
Yes, because Spring Data JPA certainly won't get into caching itself.
This is almost on the top of the priority list. Right after the current stuff I'm working which unfortunately is beyond big.
@morfsnz Spring Data JDBC does not require an additional generated (or otherwise) key for m-to-n relationships.
Things also to consider: * collection like values * values passed as query parameters where we don't know the referred property (`@Query` annotation) vs those where we do (Query derivation)....
For some database a `returning` clause could be used. For others we would need to actively select the data. I'm not sure how we should choose if we do apply...
@peteraramaldes This went into 3.0.0-RC1. It is therefore part of all 3.x releases after that including the 3.0.0 GA release.