[jira] [Resolved] (CALCITE-3050) Integrate SqlDialect and SqlParser.Config

["Julian Hyde (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CALCITE-3050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Julian Hyde resolved CALCITE-3050.
----------------------------------
       Resolution: Fixed
         Assignee: Julian Hyde  (was: Danny Chan)
    Fix Version/s: 1.20.0

Fixed in [170d5225f|https://github.com/apache/calcite/commit/170d5225fb65fd49df83d0234d8a69d11a9469c4].

> Integrate SqlDialect and SqlParser.Config
> -----------------------------------------
>
>                 Key: CALCITE-3050
>                 URL: https://issues.apache.org/jira/browse/CALCITE-3050
>             Project: Calcite
>          Issue Type: Bug
>            Reporter: Julian Hyde
>            Assignee: Julian Hyde
>            Priority: Major
>             Fix For: 1.20.0
>
>
> {{SqlDialect}} is used by the JDBC adapter to generate SQL in the target dialect of a data source. {{SqlParser.Config}} is used to set what the parser should allow for SQL statements sent to Calcite. But they both are a representation of "dialect". And they come together when we want to use a Babel parser to understand SQL statements that are meant for a data source.
> So it makes sense to integrate them, somehow. We could add a method {code}void SqlParser.ConfigBuilder.setFrom(SqlDialect dialect){code} or do it from the other end, {code}SqlDialect.configureParser(SqlParser.ConfigBuilder configBuilder){code}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)