From 78ba74c131b4147f44ac0662cf869a67bdf66486 Mon Sep 17 00:00:00 2001 From: Matthias Pigulla Date: Wed, 21 Jun 2023 19:08:09 +0200 Subject: [PATCH] Update docs/en/reference/working-with-objects.rst MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Co-authored-by: Grégoire Paris --- docs/en/reference/working-with-objects.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/reference/working-with-objects.rst b/docs/en/reference/working-with-objects.rst index 02da258643f..32d53212e68 100644 --- a/docs/en/reference/working-with-objects.rst +++ b/docs/en/reference/working-with-objects.rst @@ -314,7 +314,7 @@ association, either as the owning or inverse side, the ORM will delete rows from join tables before removing the entity itself. That means database-level ``ON DELETE RESTRICT`` constraints on join tables are not effective, since the join table rows are removed first. Removal of join table -rows happens through specialized methods in entity and collection persisterr +rows happens through specialized methods in entity and collection persister classes and take one query per entity and join table. In case the association uses a ``@JoinColumn`` configuration with ``onDelete="CASCADE"``, instead of using a dedicated ``DELETE`` query the database-level operation will be