Save(List) vs save(Entity) in transaction part two

Question

Question is a follow on from CrudRepository and Hibernate: save(List<S>) vs save(Entity) in transaction.

If I do not mark the following below with @Transactional. If the database connection drops or something happens as Spring Data JPA is saving a list. Will the list be rolled back or it will just be partly saved?

@Transactional
public void processData() {
   List<MyEntity> entities = ....;
   MyEntityRepository.save(entities);
}

is this method part of a transaction? if yes, then it will be rolled-back. — Vishrant, Feb 26 '19 at 16:25

score 2 · Accepted Answer · answered Feb 26 '19 at 14:51

Methods provided by CrudRepository are already transactional.

This is not needed at all, just take a look at this implementation. All the methods delete, deleteAll,saveAllare annotated with@Transactional`. This means, that default implementation already takes it into account.

Actually whereever there is no @Transactional annotation, the default @Transactional(readOnly = true), that is on the class level is used.

score 1 · Answer 2 · answered Feb 26 '19 at 14:39

It depends heavily on the MyEntityRepository implementation.

E.g. If it is generated by spring as a SimpleJpaRepository then it will be rollbacked. Because as shown in the linked question the save() method is also annotated with @Transactional:

@Transactional
public <S extends T> List<S> save(Iterable<S> entities) {}

But for every other implementation? I would say that behaviour is undefined

Save(List) vs save(Entity) in transaction part two

2 Answers2