From b1319ef69bfaea687c424c1c040e08a12854c0c1 Mon Sep 17 00:00:00 2001 From: Alexander Berl Date: Sun, 7 Jun 2020 11:34:18 +0200 Subject: [PATCH] Replace "Blacklist" with "Banlist" in join example --- .../reference/dql-doctrine-query-language.rst | 22 +++++++++---------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/docs/en/reference/dql-doctrine-query-language.rst b/docs/en/reference/dql-doctrine-query-language.rst index 577a02a15d0..78a8a2f2a06 100644 --- a/docs/en/reference/dql-doctrine-query-language.rst +++ b/docs/en/reference/dql-doctrine-query-language.rst @@ -529,26 +529,26 @@ Joins between entities without associations were not possible until version .. code-block:: php createQuery('SELECT u FROM User u JOIN Blacklist b WITH u.email = b.email'); + $query = $em->createQuery('SELECT u FROM User u JOIN Banlist b WITH u.email = b.email'); With an arbitrary join the result differs from the joins using a mapped property. The result of an arbitrary join is an one dimensional array with a mix of the entity from the ``SELECT`` and the joined entity fitting to the filtering of the query. In case of the example with ``User`` -and ``Blacklist``, it can look like this: +and ``Banlist``, it can look like this: - User -- Blacklist -- Blacklist +- Banlist +- Banlist - User -- Blacklist +- Banlist - User -- Blacklist -- Blacklist -- Blacklist +- Banlist +- Banlist +- Banlist -In this form of join, the ``Blacklist`` entities found by the filtering in the ``WITH`` part are not fetched by an accessor -method on ``User``, but are already part of the result. In case the accessor method for Blacklists is invoked on a User instance, -it loads all the related ``Blacklist`` objects corresponding to this ``User``. This change of behaviour needs to be considered +In this form of join, the ``Banlist`` entities found by the filtering in the ``WITH`` part are not fetched by an accessor +method on ``User``, but are already part of the result. In case the accessor method for Banlists is invoked on a User instance, +it loads all the related ``Banlist`` objects corresponding to this ``User``. This change of behaviour needs to be considered when the DQL is switched to an arbitrary join. .. note::