New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix bug when using Result Cache with Query::toIterable #8495
Conversation
toIterable
toIterable
Whyy???
|
e85e0be
to
9d57e0f
Compare
Adjusted a bit test, squashed it in 3 commits (add test, fix bug, add typehints). I hope it's all good now. :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks good to me, although I would squash the failing test and it fix in just one commit: it would not make sense to revert one without also reverting the other. Also, tests should pass on every commit IMO.
My logic behind this is that somebody could provide better implementation of fix and that would required reverting the fix, but not and the test. :) |
Isnt adding types a bc break? Hydrators are a regular extension point of the ORM so we need to be extra careful. |
@beberlei they all are in an |
I understand and agree that internal classes can have changes that are usually considered a BC break, but all those other type hints and return types are out of scope for the fix and don't add anything to the bugfix. |
@Warxcell let's drop that third commit then? |
9d57e0f
to
a81aff0
Compare
Done. :( |
a81aff0
to
897f271
Compare
Signed-off-by: Warxcell <warxcell@gmail.com>
897f271
to
930859f
Compare
Thanks @Warxcell ! |
Argument 1 passed to Doctrine\ORM\Internal\Hydration\AbstractHydrator::toIterable() must implement interface Doctrine\DBAL\Driver\Statement, instance of Doctrine\DBAL\Cache\ResultCacheStatement given, called in /app/vendor/doctrine/orm/lib/Doctrine/ORM/AbstractQuery.php on line 1010