source keyword no longer leads to syntax error #99
Conversation
This file contains 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
…on' into 96-parser-error-when-selecting-from-information_schema-views
Dtenwolde
deleted the
96-parser-error-when-selecting-from-information_schema-views
branch
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.
Fixes #95
Fixes #96
The "source" keyword was leading to a syntax error when not used as an alias with the
ASbefore it.select 1 sourcewould lead to this error for instance. This was happening in the "referential_constraints" which happened when querying a table that does not exist for example. I made a PR in DuckDB duckdb/duckdb#10848 and if it gets accepted then it will be fixed for v0.10.1.