We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
current_schema
While looking for available global variables, I noticed current_schema is not in sys.keywords (Oct2020 5e7ef9c3f0bd):
sys.keywords
sql>select distinct * from sys.keywords where keyword ilike '%current%'; +-------------------+ | keyword | +===================+ | CURRENT | | CURRENT_DATE | | CURRENT_ROLE | | CURRENT_TIME | | CURRENT_TIMESTAMP | | CURRENT_USER | +-------------------+
Why is current_schema not a reserved keyword? While it seems to behave like one:
sql>create table t (current_schema string); #2021-03-30 14:44:16: client1: createExceptionInternal: !ERROR: ParseException:SQLparser:42000!syntax error, unexpected CURRENT_SCHEMA, expecting FOREIGN or PRIMARY or UNIQUE in: "create table t (current_schema" syntax error, unexpected CURRENT_SCHEMA, expecting FOREIGN or PRIMARY or UNIQUE in: "create table t (current_schema" sql>create table t ("current_schema" string); operation successful
The text was updated successfully, but these errors were encountered:
Add more missing keywords into sys.keywords table. This fixes bug #7093
59a1de4
No branches or pull requests
While looking for available global variables, I noticed
current_schema
is not insys.keywords
(Oct2020 5e7ef9c3f0bd):Why is
current_schema
not a reserved keyword? While it seems to behave like one:The text was updated successfully, but these errors were encountered: