Use scientific Decimal rendering for inline literals#276
Merged
Conversation
ruslandoga
commented
May 7, 2026
This was referenced May 7, 2026
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
1 participant
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.
Updates inline Decimal literal rendering to use Decimal scientific notation, matching the compact rendering approach now used by Ch query params.
Keeps strict Decimal precision and scale validation for typed placeholders, while allowing inline over-limit literals to be sent compactly for ClickHouse to handle.
Requires Ch ~> 0.8.2, which includes the corresponding query parameter encoding change.
Validation: focused Decimal connection tests pass.