Fix int64/uint64 type inference to use BIGINT instead of INTEGER #313
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.
Summary
strconv.Itoa(int(value))which truncates large valuesconvertNamedValuesToSparkParamsto prevent panic whenParameter.Valueis not a stringProblem
When inserting int64/uint64 values into BIGINT columns, the driver was sending them with type
INTEGERinstead ofBIGINT, causing the server to reject large values with error:Test plan
TestParameter_BigInt)🤖 Generated with Claude Code