From 685107d4e16f34800a5c78b92dd33a24b36f4ef1 Mon Sep 17 00:00:00 2001
From: Jens Schauder <jschauder@vmware.com>
Date: Tue, 17 Oct 2023 12:46:14 +0200
Subject: [PATCH] Improved documentation of deleteAllInBatch.

Closes #3198
---
 .../springframework/data/jpa/repository/JpaRepository.java    | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/spring-data-jpa/src/main/java/org/springframework/data/jpa/repository/JpaRepository.java b/spring-data-jpa/src/main/java/org/springframework/data/jpa/repository/JpaRepository.java
index 062c41ea6..b138c6b0c 100644
--- a/spring-data-jpa/src/main/java/org/springframework/data/jpa/repository/JpaRepository.java
+++ b/spring-data-jpa/src/main/java/org/springframework/data/jpa/repository/JpaRepository.java
@@ -79,7 +79,9 @@ public interface JpaRepository<T, ID> extends ListCrudRepository<T, ID>, ListPag
 	 * Deletes the given entities in a batch which means it will create a single query. This kind of operation leaves JPAs
 	 * first level cache and the database out of sync. Consider flushing the {@link EntityManager} before calling this
 	 * method.
-	 *
+	 * <p>
+	 * It will also NOT honor cascade semantics of JPA, nor will it emit JPA  lifecycle events.
+	 *</p>
 	 * @param entities entities to be deleted. Must not be {@literal null}.
 	 * @since 2.5
 	 */