You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a fetch=EAGER association is filtered using WITH, it raises an error unless fetch mode is overridden by calling setFetchMode(LAZY) over the association.
vendor/bin/phpunit --filter testSubselectFetchJoinWithAllowedWhenOverriddenNotEagerPaginator
There was 1 error:
1) Doctrine\Tests\ORM\Functional\EagerFetchCollectionTest::testSubselectFetchJoinWithAllowedWhenOverriddenNotEagerPaginator
Doctrine\ORM\Query\QueryException: Associations with fetch-mode=EAGER may not be using WITH conditions in "Doctrine\Tests\ORM\Functional\EagerFetchChild#owner".
The text was updated successfully, but these errors were encountered:
aprat84
added a commit
to aprat84/orm
that referenced
this issue
Nov 28, 2024
Bug Report
Summary
This is related to issue #11128 and PR #11445.
When a
fetch=EAGER
association is filtered usingWITH
, it raises an error unless fetch mode is overridden by callingsetFetchMode(LAZY)
over the association.This worked well after the fix in #11445.
Somehow, in 2.20.x and 3.3.x this bug returned, partially, only when using
Paginator
withfetchJoinCollection
parameter set totrue
.Seems like #11188 introduced this bug.
Current behavior
An exception is raised even when fetch mode is overridden.
Expected behavior
It should work the same with or without pagination.
How to reproduce
See test in https://github.com/aprat84/orm/tree/gh-11741
The text was updated successfully, but these errors were encountered: