Bug: Missing implicite entityManager.flush() before storedprocedure call and Spring-Data Repository

[ere-one]

Bug: Missing implicite entityManager.flush() before storedprocedure call and Spring-Data Repository

[mp911de]

The short answer: We cannot know when to call flush.

The longer variant: Spring Data JPA adopts naturally JPA patterns and therefore it does not want to enforce flushing on each operation to slow down your application. As we do not know the order in which you're calling repositories, updating entities and such, we cannot flush for you. That is something that you need to control from your application as only your application known the appropriate time for flushing.

If we would call flush every time someone calls a stored procedure, we would impose a lot of implicit traffic and we would change the application state in a potentially breaking way.

[schauder]

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

This is a non sequitur. Spring Data JPA is not a JPA implementation. Hibernate and Eclipse are.

[ere-one]

@mp911de
Hmm, in case of JPA Repository using @query (including 'nativeQuery') you some how knows it and triggers the flush(). Your above arguments are applieble to @query as well. IMHO this should be the same with @procedure.