Missing implicite entityManager.flush() before storedprocedure call and Spring-Data Repository about spring-data-jpa HOT 2 CLOSED

Thanks for getting in touch. We prefer to use GitHub issues only for bugs and enhancements. The question on SO seems to have been answered already.

from spring-data-jpa.

Actually it is a bug in the Sppring Data JPA Repository. Because entityManager.flush() must be called implicitally by a vendor if FlushModeType.AUTO is used, see related JEE API Doc:
https://docs.oracle.com/javaee%2F7%2Fapi%2F%2F/javax/persistence/FlushModeType.html

"... the persistence provider is responsible for ensuring that all updates to the state of all entities in the persistence context which could potentially affect the result of the query are visible to the processing of the query. ..."

In case of a Spring-Data JPA Repository methods annotated with @query, the entityManager.flush() will be called implicitally before executing the query, so the query can use/see the changes made in the same transaction.
In case of a Spring-Data JPA Repository methods annotated with @procedure the entityManager.flush() will not be called implicitally, so the stored procedure, in which queries may be used, will not use/see changes made in the same transaction.

We use Spring-Boot 2.7.10

from spring-data-jpa.