DDC-2530: Fetch eager in onetomany is not storing the collection resulting in same query being executed twice #3175

New Issue

admin · 2026-01-22T14:14:33+01:00

admin commented

2026-01-22 14:14:33 +01:00

Originally created by @doctrinebot on GitHub (Jun 25, 2013).

Originally assigned to: @beberlei on GitHub.

Jira issue originally created by user legolas:

I have two entities Users and Bugs (A user can report multiple bugs) sharing bidirectional onetomany relation between them. On the inverse side of the relation I have put fetch = eager as given below.

class Users{
     /****
     * @ORM\OneToMany(targetEntity="Bugs", mappedBy="reporter",fetch="EAGER")
     * @var Bugs[]
     ****/
     private $reportedBugs;
}

Now when I run this code:

$user = $em->find("ZC\Entity\Users", 7);

Firstly user entity is fetched from the user table with id = 7. Then it looks for the bugs associated with user_id = 7 in the bugs table. This seems to be the expected behavior where due to the eager fetch the related associations are automatically loaded. What seems to be the bug is, after this when the user's reported bugs are called, an unnecessary query is executed which again looks for the bugs in the bugs table related to the user_id = 7 and that is basically the same query as before. This is just a redundant query. So the eager fetch should have stored the associated bugs in the first call itself and the subsequent call to the reported bugs should just return the already fetched entities.

Originally created by @doctrinebot on GitHub (Jun 25, 2013). Originally assigned to: @beberlei on GitHub. Jira issue originally created by user legolas: I have two entities Users and Bugs (A user can report multiple bugs) sharing bidirectional onetomany relation between them. On the inverse side of the relation I have put fetch = eager as given below. ``` class Users{ /**** * @ORM\OneToMany(targetEntity="Bugs", mappedBy="reporter",fetch="EAGER") * @var Bugs[] ****/ private $reportedBugs; } ``` Now when I run this code: ``` $user = $em->find("ZC\Entity\Users", 7); ``` Firstly user entity is fetched from the user table with id = 7. Then it looks for the bugs associated with user_id = 7 in the bugs table. This seems to be the expected behavior where due to the eager fetch the related associations are automatically loaded. What seems to be the bug is, after this when the user's reported bugs are called, an unnecessary query is executed which again looks for the bugs in the bugs table related to the user_id = 7 and that is basically the same query as before. This is just a redundant query. So the eager fetch should have stored the associated bugs in the first call itself and the subsequent call to the reported bugs should just return the already fetched entities.

admin added the Bug label 2026-01-22 14:14:33 +01:00

admin closed this issue

2026-01-22 14:14:33 +01:00

admin commented

2026-01-22 14:14:34 +01:00