DDC-2915: When there are 2 identical aliases in an object hydrated dql query tied to a relation, some times it retrives an empty relation #3674

doctrinebot opened this Issue Jan 14, 2014 · 2 comments

2 participants


Jira issue originally created by user willf1976:


I recently had a problem with a Dql query I wrote where when I had a typo in my select which resulted in a very odd behavior. At a predictable row number one of the relations wouldn't hydrate.

This resulted in the fatal error when I tried to access the relation like so: $row->getLolGameSize()->getName()

Call to a member function getName() on a non-object

Here is the query that causes the problem -- removing the second reference to lgs in the select fixes the problem.

SELECT lst, ls, lr, lt, lstlt, lgt, lgs, lgs, ats
FROM Team\Entity\Lolsummonertournament lst
INNER JOIN lst.lolSummoner ls
INNER JOIN ls.lolRank lr
INNER JOIN ls.lolTier lt
LEFT JOIN lst.lolTier lstlt
INNER JOIN lst.lolGameType lgt
INNER JOIN lst.lolGameSize lgs
INNER JOIN lst.attendanceStatus ats
WHERE lst.tournament = :tournamentId
AND ls.summonerId IS NOT NULL
ORDER BY ls.mmr desc

All the best


Comment created by @ocramius:

Fetch joining on filtered associations is very dangerous and unsupported.


Issue was closed with resolution "Invalid"

@Ocramius Ocramius was assigned by doctrinebot Dec 6, 2015
@doctrinebot doctrinebot closed this Dec 6, 2015
@doctrinebot doctrinebot added the Bug label Dec 7, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment