-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Portability Statement still fetches all data in iterator mode #3114
Comments
morozov
added a commit
to morozov/dbal
that referenced
this issue
Apr 22, 2018
morozov
added a commit
to morozov/dbal
that referenced
this issue
Apr 22, 2018
morozov
added a commit
to morozov/dbal
that referenced
this issue
Apr 22, 2018
morozov
added a commit
to morozov/dbal
that referenced
this issue
Apr 22, 2018
morozov
added a commit
to morozov/dbal
that referenced
this issue
Apr 28, 2018
morozov
added a commit
that referenced
this issue
Apr 29, 2018
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
As of #2718, in iterator mode, statements are supposed to fetch entries one by one for more efficient memory usage.
Apparently, the portability statement wrapper still fetches all entries in memory:
dbal/lib/Doctrine/DBAL/Portability/Statement.php
Lines 140 to 145 in 11037b4
It renders the entire optimization useless if the portability wrapper is used.
The text was updated successfully, but these errors were encountered: