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

Document that JpaSpecificationExecutor.delete(…) uses CriteriaDelete and hence Cascades are not considered.

Browse Source 
Closes #2936
This commit is contained in:
Mark Paluch
2023-05-10 10:44:29 +02:00
parent 3a1812ca6b
commit b9bd0e70e0
1 changed files with 12 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

12
spring-data-jpa/src/main/java/org/springframework/data/jpa/repository/JpaSpecificationExecutor.java
View File

@@ -15,6 +15,10 @@
*/
package org.springframework.data.jpa.repository;
import jakarta.persistence.criteria.CriteriaBuilder;
import jakarta.persistence.criteria.CriteriaQuery;
import jakarta.persistence.criteria.Root;
import java.util.List;
import java.util.Optional;
import java.util.function.Function;
@@ -89,6 +93,14 @@ public interface JpaSpecificationExecutor<T> {
/**
* Deletes by the {@link Specification} and returns the number of rows deleted.
* <p>
* This method uses {@link jakarta.persistence.criteria.CriteriaDelete Criteria API bulk delete} that maps directly to
* database delete operations. The persistence context is not synchronized with the result of the bulk delete.
* <p>
* Please note that {@link jakarta.persistence.criteria.CriteriaQuery} in,
* {@link Specification#toPredicate(Root, CriteriaQuery, CriteriaBuilder)} will be {@literal null} because
* {@link jakarta.persistence.criteria.CriteriaBuilder#createCriteriaDelete(Class)} does not implement
* {@code CriteriaQuery}.
*
* @param spec the {@link Specification} to use for the existence check. Must not be {@literal null}.
* @return the number of entities deleted.