Skip to content

fix(write): allow exact large integers in mixed numeric columns - #76

Open
efegokdemir wants to merge 1 commit into
Basekick-Labs:mainfrom
efegokdemir:efe/exact-mixed-numbers
Open

efegokdemir wants to merge 1 commit into
Basekick-Labs:mainfrom
efegokdemir:efe/exact-mixed-numbers

Conversation

@efegokdemir

Copy link
Copy Markdown
Contributor

JSON writes rejected mixed columns such as [9007199254740994, 1.5] even though the integer converts exactly to float64. Check that conversion to float64 and back preserves each integer, with an explicit range check at the positive int64 boundary. Adds regression tests for both value orders, nulls, integer-only columns and the uploaded MessagePack bytes.

Tested on macOS arm64 with Go 1.27.1: go test -race -count=1 ./..., go vet ./..., go build ./..., gofmt -l . and git diff --check passed. Regression tests reproduced the rejection before the fix. Linux CI and the GoReleaser snapshot have not been run locally.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant