You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Most (if not all) databases have a set of built-in functions. Whether the name of a built-in function in an SQL query should be regarded as a keyword or identifier could potentially depend on the SQL dialect. But for dialects where these are identifiers, it would make sense if they would get quoted if RenderQuotedNames#ALWAYS is specified in the Settings.
The text was updated successfully, but these errors were encountered:
This change is included in #9931, when (if) we introduce a new concept of a "system name", i.e. a special kind of name for a built-in function.
I think that quoting these is almost never a good idea, even in dialects that have an actual function in the catalog backing the built-in function. There are always exceptions, and special functions that are not part of the catalog after all, but are translated by the parser to some other internal function syntax.
Most (if not all) databases have a set of built-in functions. Whether the name of a built-in function in an SQL query should be regarded as a keyword or identifier could potentially depend on the SQL dialect. But for dialects where these are identifiers, it would make sense if they would get quoted if
RenderQuotedNames#ALWAYS
is specified in theSettings
.The text was updated successfully, but these errors were encountered: