You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Jesus Camacho Rodriguez (JIRA)" <ji...@apache.org> on 2019/01/07 20:55:00 UTC
[jira] [Resolved] (CALCITE-2623) Updating unparseCall() in
SqlDialect(s) for dialect specifc SqlNode unparsing
[ https://issues.apache.org/jira/browse/CALCITE-2623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jesus Camacho Rodriguez resolved CALCITE-2623.
----------------------------------------------
Resolution: Fixed
Fix Version/s: 1.19.0
Fixed in [13fca96|https://gitbox.apache.org/repos/asf?p=calcite.git;a=commit;h=13fca96]. Thanks for your contribution [~Krishnakant A]
> Updating unparseCall() in SqlDialect(s) for dialect specifc SqlNode unparsing
> -----------------------------------------------------------------------------
>
> Key: CALCITE-2623
> URL: https://issues.apache.org/jira/browse/CALCITE-2623
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Reporter: KrishnaKant Agrawal
> Assignee: Julian Hyde
> Priority: Minor
> Labels: pull-request-available
> Fix For: 1.19.0
>
>
> Owing to the syntactical differences between Calcite SQL and certain other Dialects, emulation for SqlNode unparsing needs to be added based on the Dialect in RelToSqlConcverter.
> Saw some code in PostgreSqlDialect which is already doing this.
> Changes in other Dialects can follow suit.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)