Doctrine 2.5 Unexpected Association Sampling Behavior [Symfony 3]

Question

I have three objects connected in this way:

Don't worry, I made associations using annotations, but I thought the next mix would be easier / cleaner to identify my problem.

Post @ORM\ManyToOne(targetEntity="User", fetch="EAGER") - author User @ORM\OneToOne(targetEntity="Vip", mappedBy="user", fetch="EAGER") - vip Vip # Notice that the primary key of vip is a foreign key on User primary @ORM\id @ORM\OneToOne(targetEntity="User", inversedBy="peliqan", fetch="EAGER") @ORM\JoinColumn(name="user_id", referencedColumnName="id", nullable=false) - user 

As you can see, everything is set up to be impatient.

What I need?

I would like to receive message sets along with and Users & Vip ONLY using a single request . (see edit)

Right now, for each message entry, I get one additional request:

 SELECT t0.valid AS valid_1, ... FROM vip t0 INNER JOIN user t10 ON t0.user_id = t10.id WHERE t0.user_id = ? 

when:

• I'm doing this

   $results = $qb ->select('ps') ->leftJoin('ps.author','u')->addSelect('u') ->add('where', $qb->expr()->in('ps.id', $ids)) ->getQuery()->getResult(); 

• and even when I try to apply FETCH_EAGER mode like this

   ->getQuery() ->setFetchMode('AppBundle\Entity\User', 'vip', ClassMetadata::FETCH_EAGER) ->getResult(); 

Note:
I managed to get rid of the extra request enforcingQuery::HYDRATE_ARRAY when calling getResult() .
Requests disappeared, which saved a third from the original time.
The disadvantage here is that when you remove the association as an array, I could no longer use Symfony\Component\Serializer\Annotation\Groups Groups to filter the properties of objects and had to manually edit the result set to remove / convert some values.

EDIT

The wilt response is appropriate for the original message. I did not solve my problem correctly. I said that I wanted to get Vip information because I thought it was a good way to get rid of the extra request that I am talking about above. Actually, I don't need information about Vip, but omitting ->leftJoin('u.vip','v')->addSelect('v') makes the doctrine issue an additional request that collects Vip information! Is there a way to prevent the doctrine of fulfilling this request?

Answer 1

There are two types of connection requests in Doctrine2:

1) Regular connections
2) Get connections

Mark the documentation section 14.2.2. Joins for more details.

So, if you want to receive vips connections, you must addSelect and leftJoin them in your request as follows:

 $results = $qb ->select('ps') ->addSelect('u')->leftJoin('ps.author','u') ->addSelect('v')->leftJoin('u.vip','v') ->add('where', $qb->expr()->in('ps.id', $ids)) ->getQuery()->getResult(); 

---

UPDATE

Update after your comment:

I thought vip in the result set would be the best way to get rid of the extra request

You cannot get rid of the extra request because you cannot be too lazy to load the other side of the one-to-one relationship. See also this post :

This is the expected behavior. The flipsides of one-to-one associations cannot be lazy, technically. There is no foreign key on the back side, so it is impossible to decide if a proxy server or not. We must request a join object or join it. Note that this only affects the backs of unambiguous associations, that is, in fact, only the back of bi-directional one-to-one associations.

• The solution may lie in the inverse relationship, so the user becomes the owner of the relationship. In this case, you can at least lazy-load the Vip inside your User object. The problem with lazy loading would be moved to the side of Vip , which means that you can no longer lazy-load User in Vip .

• Otherwise, you can return a partial object request to prevent the Vip from loading, but in general you have to be very careful with this approach.