feat: Support SQL VALUES
clause and inline renaming of columns in CTE & derived table definitions
#16851
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.
Adds new SQL interface support for...
VALUES
1 clause (doesn't support inline literal casts or typed literals yet).Example
Standalone
VALUES
clause:Select from
VALUES
, applying column names with the table alias:Demonstrate/stress-test name/alias resolution; select from inner
VALUES
and show that we successfully map column/table names through multiple levels of nested CTEs and derived table column aliasing.Footnotes
PostgreSQL VALUES clause: https://www.postgresql.org/docs/current/sql-values.html ↩