-
Notifications
You must be signed in to change notification settings - Fork 78
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
Only quote non-syntactic names and reserved words in dbQuoteIdentifier #427
Comments
Interesting. Should we experiment with an |
Why wouldn't this just be a method of |
dbplyr will have to special-case anyway, a separate new experimental entry point is easier to deprecate/change later on. IIUC, |
The other thing to consider -- if we aim to build SQL that is "pretty enough" to be used permanently and remain unchanged for years, what happens if SQLite introduces a keyword later on? If it's only for aesthetic purposes, I agree it's useful. Should we do this for duckdb too? |
I think adding reserved words would be pretty rare, as it would potentially break lots of existing SQL. For duckdb, see duckdb/duckdb#3718 |
Using https://www.sqlite.org/c3ref/keyword_check.html to capture all reserved words.
This isn't very important, but it does help dbplyr generate more natural SQL.
The text was updated successfully, but these errors were encountered: