Bump to v1.5.3#139
Merged
Merged
Conversation
1) Let TYPE_VARIANT work for TypeInfo and ColumnTypeInfo metadata. 2) Keep VARIANT scan, bind, and appender value paths explicitly unsupported. The practical benefit is better metadata without pretending value decoding exists.
Add regression coverage for appender creation, parameter binding, and typed value hints so VARIANT stays metadata-only until value helpers exist. Exclude VARIANT from primitive value creation as a defensive guard.
taniabogatsch
approved these changes
May 21, 2026
And document follow-up points for VARIANT bind and appender write support.
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
2 participants
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.
Bindings: duckdb/duckdb-go-bindings#88