Repository navigation
Encode negative-scale BigDecimal values correctly - #1776
Open
sharanggupta wants to merge 1 commit into
Open
sharanggupta wants to merge 1 commit into
sharanggupta wants to merge 1 commit into
Conversation
The scale byte was clamped to zero but the unscaled value was not multiplied back, so 1.5E+3 (1500 after stripTrailingZeros) was sent as 15. Signed-off-by: Sharang Gupta <sharang@sharanggupta.dev> Assisted-by: Anthropic Claude (claude-opus-5-5)
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
A
BigDecimalparameter with a negative scale, whichstripTrailingZeros()produces routinely, is sent with its scale clamped to zero but its unscaled value unchanged, sonew BigDecimal("1500").stripTrailingZeros()(15E+2) is stored as15. The value is now rescaled to zero before encoding. Verified against the SQL Server engine (Azure SQL Edge) with the module'sinit.sql; the data type tests pass apart from the JSON ones, which need SQL Server 2025.