-
-
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
Deprecate Statement::fetch* methods in favor of Result::fetch* counterparts #4554
Comments
…eprecation identifiers.
[GH-4554] Deprecate all Statement::fetch* in favor of Result::fetch*
Merged #4555 |
@beberlei you deprecated them but
Not sure if this was desired behaviour, if I'm in some kind of a limbo
Just as a notice, I'm unable to upgrade to doctrine/dbal 3 as doctrine migrations 3.1 dont support it |
I had some problems some weeks ago fixing those deprecations. Now everything is OK. Having the GitHub issue link in the deprecation is really nice. Thanks, @beberlei 🙂 |
Why nobody likes the native PHP PDO structure and every framework wants to change it and use a different one 😅 hard to understand... |
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. |
Deprecation
Summary
Deprecate all new
Statement::fetch*
methods that should be called from aResult
instead. TheResult
is returned as an object fromStatement::execute
. Work on the forward compatibility for theResult
interface was done in #4529.Old code
New code
The text was updated successfully, but these errors were encountered: