-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Add support for PostgreSQL-style shorthand casts #27392
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
martint
wants to merge
2
commits into
trinodb:master
Choose a base branch
from
martint:cast-shorthand
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
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
Standard SQL supports static method calls on types via the :: operator.
While this syntax is generally incompatible with PostgreSQL shorthand cast
syntax, there's a subset of that can be safely repurposed to support that
functionality.
The SQL specification defines static method calls as:
<static method invocation> ::=
<path-resolved user-defined type name> <double colon> <method name>
[ <SQL argument list> ]
where <path-resolved user-defined type name> translates to:
<user-defined type name> ::=
[ <schema name> <period> ] <qualified identifier>
To support casts, we need to extend the rule to support arbitrary expressions
as the target of the invocation. To disambiguate a static method call from
a cast, we distinguish between type-producing expressions and expressions that
produce regular values. For the latter, if the method matches the name of a
well-known type, we treat it as a cast. Otherwise, the expression assumed
to be a static method call and fail the evaluation with a "not yet supported"
error.
One limitation is that casts are only supported for simple types. Parametric
types are not yet supported, but it wouldn't be too hard to add. Types whose
name don't match the syntax of SQL function calls are not supported either
and will be harder to support. That will require introducing type-producing
expressions into the language and making types first-class expressions.
findepi
reviewed
Nov 21, 2025
findepi
reviewed
Nov 21, 2025
core/trino-grammar/src/main/antlr4/io/trino/grammar/sql/SqlBase.g4
Outdated
Show resolved
Hide resolved
core/trino-main/src/main/java/io/trino/sql/analyzer/ExpressionAnalyzer.java
Outdated
Show resolved
Hide resolved
core/trino-main/src/main/java/io/trino/sql/analyzer/ExpressionAnalyzer.java
Outdated
Show resolved
Hide resolved
core/trino-main/src/main/java/io/trino/sql/analyzer/ExpressionAnalyzer.java
Outdated
Show resolved
Hide resolved
core/trino-main/src/main/java/io/trino/sql/analyzer/ExpressionAnalyzer.java
Show resolved
Hide resolved
core/trino-main/src/main/java/io/trino/sql/analyzer/ExpressionAnalyzer.java
Show resolved
Hide resolved
core/trino-main/src/test/java/io/trino/operator/scalar/TestStaticMethodCall.java
Show resolved
Hide resolved
f712f7a to
0c9ebcf
Compare
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.
Standard SQL supports static method calls on types via the :: operator. While this syntax is generally incompatible with PostgreSQL shorthand cast syntax, there's a subset of that can be safely repurposed to support that functionality.
The SQL specification defines static method calls as:
where
<path-resolved user-defined type name>translates to:To support casts, we need to extend the rule to support arbitrary expressions as the target of the invocation. To disambiguate a static method call from a cast, we distinguish between type-producing expressions and expressions that produce regular values. For the latter, if the method matches the name of a well-known type, we treat it as a cast. Otherwise, the expression assumed to be a static method call and fail the evaluation with a "not yet supported" error.
One limitation is that casts are only supported for simple types. Parametric types are not yet supported, but it wouldn't be too hard to add. Types whose name don't match the syntax of SQL function calls are not supported either and will be harder to support. That will require introducing type-producing expressions into the language and making types first-class expressions.
Fixes #23795
Release notes
(x) Release notes are required, with the following suggested text: