Spring/spring-data-jpa
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Refine performance requirements on derived delete queries.

Browse Source 
Closes #3177
This commit is contained in:
Mark Paluch
2025-01-31 10:58:58 +01:00
parent f9e04c549c
commit 85710568a0
1 changed files with 3 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
src/main/antora/modules/ROOT/pages/jpa/query-methods.adoc
View File

@@ -629,6 +629,9 @@ To make sure lifecycle queries are actually invoked, an invocation of `deleteByR
In fact, a derived delete query is a shortcut for running the query and then calling `CrudRepository.delete(Iterable<User> users)` on the result and keeping behavior in sync with the implementations of other `delete(…)` methods in `CrudRepository`.
NOTE: When deleting a lot of objects you will need to consider the performance implications to ensure sufficient memory availability.
All resulting objects are loaded into memory before being deleted and are held in the session until flushing or completing the transaction.
[[jpa.query-hints]]
== Applying Query Hints
To apply JPA query hints to the queries declared in your repository interface, you can use the `@QueryHints` annotation. It takes an array of JPA `@QueryHint` annotations plus a boolean flag to potentially disable the hints applied to the additional count query triggered when applying pagination, as shown in the following example: