feat: Support SQL
"SELECT" with no tables, optimise registration of globals
#16836
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.
Closes #16826.
SELECT 1 AS "one", 2.0 AS "two"
(eg: project literals without reference to an existing table)1.Also:
SQLContext
with globals (cleaner/better handling of reserved SQL keywords).SQLContext
footgun; can only automatically register non-Polars globals viapl.sql
orSQLContext.execute_global
now; this ensures that we only register objects referenced in an actual query.Footnotes
PostgreSQL "SELECT" syntax: https://www.postgresql.org/docs/current/sql-select.html#:~:text=SELECT%20retrieves%20rows%20from%20zero%20or%20more%20tables. ↩