From ba3eb0860240ad757816b1f82c1e974615b0d61a Mon Sep 17 00:00:00 2001 From: Konrad Abicht Date: Fri, 28 Jun 2024 08:02:28 +0200 Subject: [PATCH] working-with-objects.rst: added missing white space --- 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 cc107e6e174..c4175a9114d 100644 --- a/docs/en/reference/working-with-objects.rst +++ b/docs/en/reference/working-with-objects.rst @@ -341,7 +341,7 @@ in multiple ways with very different performance impacts. 1. If an association is marked as ``CASCADE=REMOVE`` Doctrine ORM will fetch this association. If its a Single association it will pass this entity to - ``EntityManager#remove()``. If the association is a collection, Doctrine will loop over all its elements and pass them to``EntityManager#remove()``. + ``EntityManager#remove()``. If the association is a collection, Doctrine will loop over all its elements and pass them to ``EntityManager#remove()``. In both cases the cascade remove semantics are applied recursively. For large object graphs this removal strategy can be very costly. 2. Using a DQL ``DELETE`` statement allows you to delete multiple