Extend output buffer sizes with SQL decimals or numerics #775
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.
When the sql type is strictly defined (e.g. decimal(1,0)), the column size is only 1. Since decimals and numerics are treated as strings, the initial values of the output params with trailing zeros are dropped in convert_to_string() as well.
Thus the output buffer sizes are not enough for negative numbers (with a negative sign) and/or decimals.
See the similar issue #705
This change is