Fix doctrine/dbal
deprecation using Statement::executeQuery
#18429
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Deprecation warning when
doctrine/dbal >= 3.4.*
.In Symfony docs,executeQuery() is mentionned here : Querying with SQL.
But since
3.4.*
passing parameters toStatement::execute*()
functions is deprecated bydoctrine/dbal
with this warning:User Deprecated: Passing $params to Statement::executeQuery() is deprecated. Bind parameters using Statement::bindParam() or Statement::bindValue() instead. (Statement.php:212 called by User.php:40, https://github.com/doctrine/dbal/pull/5556, package doctrine/dbal)
.I've already ask in the DBAL PR concerned how to use
executeQuery
from now on.(in the same PR)
So, after having tested it in a prod project, I propose an update of the doc in this sense.
Thanks again @derrabus 🙏