Skip to content

Commit c37b115

Browse files
authored
Merge pull request #11534 from k00ni/patch-1
working-with-objects.rst: added missing white space
2 parents c1bb2cc + 19129e9 commit c37b115

File tree

1 file changed

+5
-4
lines changed

1 file changed

+5
-4
lines changed

docs/en/reference/working-with-objects.rst

+5-4
Original file line numberDiff line numberDiff line change
@@ -338,10 +338,11 @@ Performance of different deletion strategies
338338
Deleting an object with all its associated objects can be achieved
339339
in multiple ways with very different performance impacts.
340340

341-
1. If an association is marked as ``CASCADE=REMOVE`` Doctrine ORM
342-
will fetch this association. If its a Single association it will
343-
pass this entity to
344-
``EntityManager#remove()``. If the association is a collection, Doctrine will loop over all its elements and pass them to``EntityManager#remove()``.
341+
1. If an association is marked as ``CASCADE=REMOVE`` Doctrine ORM will
342+
fetch this association. If it's a Single association it will pass
343+
this entity to ``EntityManager#remove()``. If the association is a
344+
collection, Doctrine will loop over all its elements and pass them to
345+
``EntityManager#remove()``.
345346
In both cases the cascade remove semantics are applied recursively.
346347
For large object graphs this removal strategy can be very costly.
347348
2. Using a DQL ``DELETE`` statement allows you to delete multiple

0 commit comments

Comments
 (0)