fix: preserve nullary function metadata - #106
Merged
osipovartem merged 1 commit intoSep 18, 2026
Merged
osipovartem merged 1 commit into
osipovartem merged 1 commit into
Conversation
osipovartem
deleted the
information-schema-nullary-variadic-metadata
branch
September 18, 2026 16:49
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
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.
Which issue does this PR close?
information_schemafunction metadata.Rationale for this change
Functions whose signatures accept zero arguments can currently produce only an untyped placeholder row when
TypeSignature::get_example_types()returns no representative input types. This causes nullary scalar/window functions and aggregate signatures such asCOUNT()to lose their return type and arity metadata. Nested variadic signatures insideOneOfare also reported as non-variadic.What changes are included in this PR?
TypeSignature::OneOf.The work is limited to information-schema construction and does not affect expression evaluation or query execution hot paths.
Are these changes tested?
SQLLogicTest coverage verifies nullary scalar (
current_date), aggregate/nested variadic (count), and window (rank) metadata, including nativeSHOW FUNCTIONSoutput.cargo test --profile=ci --test sqllogictests -- information_schemacargo clippy --all-targets --all-features -- -D warningscargo fmt --all -- --checkAre there any user-facing changes?
Yes.
information_schema.routines,information_schema.parameters, andSHOW FUNCTIONSnow report return types and variadic arity for zero-argument-compatible functions instead of NULL/incomplete metadata. There are no public API changes.