This is not related to transactions not working.
Instead, it’s about Spring Data JDBC considering your instance an existing instance that needs updating (instead of inserting).
You can verify this is the problem by activating logging for org.springframework.jdbc.core.namedparam.NamedParameterJdbcTemplate
. You should see an update
but no insert
.
By default, Spring Data JDBC considers an entity as new when it has an id of an object type and a value of null
or of a primitive type (e.g. int
or long
) and a value of 0
.
If your entity has an attribute with @Version
annotation that attribute will be used to determine if the instance is a new one.
You have the following options in order to make it work:
-
Set the id to
null
and configure your database schema so that it will automatically create a new value on insert. After the save your entity instance will contain the generated value from the database.Note: Spring Data JDBC will set the id even if it is final in your entity.
-
Leave the id
null
and set it in a Before-Convert listener to the desired value. -
Let your entity implement
Persistable
. This allows you to control when an entity is considered new. You’ll probably need a listener as well so you can let the entity know it is not new any longer. -
Beginning with version 1.1 of Spring Data JDBC you’ll also be able to use a
JdbcAggregateTemplate
to do a direct insert, without inspecting the id, seehttps://jira.spring.io/browse/DATAJDBC-282
. Of course, you can do that in a custom method of your repository, as is done in this example: https://github.com/spring-projects/spring-data-examples/pull/441