Skip to content
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

User defined functions with reserved keyword names raise ParseError in BigQuery dialect #3332

Closed
sean-rose opened this issue Apr 17, 2024 · 0 comments
Assignees

Comments

@sean-rose
Copy link

While BigQuery doesn't allow reserved keywords to be used as standalone identifiers unless they're quoted, it does allow unquoted reserved keywords to be used as part of a qualified identifier (e.g. a UDF qualified with its dataset, or a subfield qualified with its parent fields).

This was originally reported in #1535 "User defined functions with keyword or built in function names throw ParseError for BigQuery dialect" (though the code snippet there only demonstrated the built-in function case, not the keyword case).

Fully reproducible code snippet

sqlglot.parse_one("SELECT assert.true(1=1)", read="bigquery")

Official Documentation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants