ORM toIterable broken due to ForwardCompatibilty result

[bobvandevijver]

The following exception occurs when using toIterable on a query generated by a repository query builder:

Argument 1 passed to Doctrine\ORM\Internal\Hydration\AbstractHydrator::toIterable() must implement interface Doctrine\DBAL\Driver\Statement, instance of Doctrine\DBAL\ForwardCompatibility\Result given, called in /var/www/some-project/vendor/doctrine/orm/lib/Doctrine/ORM/AbstractQuery.php on line 1010

The code line triggering this exception is as follows:

$userIterator = $this->userRepository->createQueryBuilder('u')->getQuery()->toIterable();

This started after upgrading this library from 1.12.1 to 1.13.0. It looks like the following line is the cause of this:

dbal/lib/Doctrine/DBAL/Connection.php

Line 1313 in 79a6a84

return $this->ensureForwardCompatibilityStatement($stmt);

Which triggers the exception finally in ORM in the AbstractQuery, where the toIterable doesn't receive the statement object it expects.

For me it looks like the ForwardCompatibilty isn't fully compatible with the statement object returned previously, so it would seem to be it needs to be fixed here? If that is not the case and this issue needs to be opened on the ORM repository, just say the word!

[TwanVermeulen]

I get a similar exception after upgrading to 1.13.0. But in a different vendor:

Argument 1 passed to Symfony\Component\Security\Acl\Dbal\AclProvider::hydrateObjectIdentities() must implement interface Doctrine\DBAL\Driver\Statement, instance of Doctrine\DBAL\ForwardCompatibility\Result given, called in /var/www/app/default/symfony-standard/app_manager/vendor/symfony/security-acl/Dbal/AclProvider.php on line 468

[mdumoulin]

@bobvandevijver Seems the issue is rather on ORM side. The AbstractHydrator::toIterable() method should rely on Doctrine\DBAL\Driver\ResultStatement instead of Doctrine\DBAL\Driver\Statement.

If I'm correct, this issue was already resolved and you can fix it by updating the ORM version : doctrine/orm@930859f#diff-f1936bc3177c94ebd06906a54a439e496b410cfee881d6740ac344f03382e0dd

[bobvandevijver]

@mdumoulin You're right, it is indeed fixed in ORM 2.8.3. 👍🏻

@TwanVermeulen Looks like there is an PR pending to fix your issue: symfony/security-acl#64

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.