[
https://issues.apache.org/jira/browse/CALCITE-6206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17807438#comment-17807438
]
Julian Hyde commented on CALCITE-6206:
--------------------------------------
I support this initiative. Calcite needs to "translate SQL expression e from
dialect X to dialect Y" in several different places: not just in RelToSql (aka
JDBC adapter) but also when receiving SQL in a particular dialect. If the
mapping is comprehensive and well-tested it will simplify code elsewhere (e.g.
in methods that override {{SqlDialect.unparseCall}}).
> Add library operator mapping for unparsing
> ------------------------------------------
>
> Key: CALCITE-6206
> URL: https://issues.apache.org/jira/browse/CALCITE-6206
> Project: Calcite
> Issue Type: Improvement
> Reporter: Tanner Clary
> Assignee: Tanner Clary
> Priority: Major
>
> [~julianhyde] and I have talked about adding the ability to reference
> cross-dialect operator aliases during unparsing so it does not need to be
> "manually added".
> For instance, if unparsing a call for the "STARTS_WITH" operator for the
> Snowflake dialect, it would be nice if there was some sort of map that could
> be referenced to see that the call should be unparsed with "STARTSWITH"
> instead.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
