Deprecate using NULL as prepared statement parameter type #5550
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.
Semantically, the NULL value of the parameter type is identical to
ParameterType::STRING
which is the default in most of the methods. Given that the parameter type is optional in all APIs, there's no point in supporting NULL. Dropping the support for NULL will make the PHP types representing prepared statement parameter types a bit simpler (see #5548).