Closed
Description
Version: spring-data-jdbc:3.5.0-M1
Currently when using the @Sequence
annotation in an entity, it seems to generate a new value on each save.
This results in an error, when trying to update an entity complaining that the newly generated id is not available in the database.
I think there should be a check, so it only generates a new value, when there is none set.