Mike Wilkes opened DATAJDBC-438 and commented
I have a Repository defined, and an entity that has a generated Id. If I create an entity with an Id that doesn't already exist (nefarious, client issue, deleted by another client are all scenarios where this could reasonably happen), and call 'save' on the repository, the method returns the object unchanged, and gives no indication that a record was not updated.
Looking internally, it appears the action does not check the 'rows updated' return from the JdbcTemplate.update method, and by default, ignores warning exceptions from SQL.
+Expected+
The 'save' gives some indication that the update did not take please because the entity is not in the DB. Something as simple as the 'save' returning null, or it could throw an exception. No strong opinion here
Affects: 1.1 GA (Moore)
Referenced from: pull request #178, and commits 92b6b04, dfaf0ac
1 votes, 2 watchers