Re-add string -> hugeint compressed materialization function#18234
Merged
Mytherin merged 1 commit intoduckdb:v1.3-ossivalisfrom Jul 14, 2025
Merged
Re-add string -> hugeint compressed materialization function#18234Mytherin merged 1 commit intoduckdb:v1.3-ossivalisfrom
Mytherin merged 1 commit intoduckdb:v1.3-ossivalisfrom
Conversation
Contributor
Collaborator
Author
|
@Tishj Thanks for the suggestion but sadly no. The functions cannot be accessed through SQL, so the SQL -> parsed plan (and vice versa) are no use. They only can only be accessed through the optimized logical plan. We can go from SQL -> serialized logical plan, but not the other way around (yet). |
Collaborator
Author
|
I just realised this should target |
e66baa2 to
34b9539
Compare
Collaborator
|
Thanks! |
github-actions bot
pushed a commit
to duckdb/duckdb-r
that referenced
this pull request
Jul 14, 2025
Re-add string -> hugeint compressed materialization function (duckdb/duckdb#18234)
github-actions bot
added a commit
to duckdb/duckdb-r
that referenced
this pull request
Jul 14, 2025
Re-add string -> hugeint compressed materialization function (duckdb/duckdb#18234) Co-authored-by: krlmlr <krlmlr@users.noreply.github.com>
ywelsch
added a commit
to ywelsch/duckdb
that referenced
this pull request
Oct 15, 2025
The patch in duckdb#18234 had a copy-paste bug. This causes clients with older plans that still use the legacy hugeint_t compression to not be compatible with DuckDB 1.4 and later.
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
3 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.
For backwards compatibility, but we never generate it. I can't add a test because we can only use this function internally, and while I can generate a plan that has it using
json_serialize_plan, we don't have ajson_execute_serialized_planfunction.Fixes https://github.com/duckdblabs/duckdb-internal/issues/5306