[
https://issues.apache.org/jira/browse/CALCITE-4614?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17347822#comment-17347822
]
Julian Hyde commented on CALCITE-4614:
--------------------------------------
This would be awesome. It's always a difficult call whether to create a new
dialect, but my impression is that Exasol does not slavishly follow another
dialect (say PostgreSQL); the the differences will tend to widen over time, and
therefore a separate dialect makes sense.
You could use a previous dialect, say Clickhouse (CALCITE-2157, commit
[39e58566|https://github.com/apache/calcite/commit/39e58566c1ac02824d99ae9260d3315539efd57e])
as a template.
> Exasol dialect implementation
> -----------------------------
>
> Key: CALCITE-4614
> URL: https://issues.apache.org/jira/browse/CALCITE-4614
> Project: Calcite
> Issue Type: New Feature
> Components: jdbc-adapter
> Reporter: TJ Banghart
> Priority: Major
>
> Exasol is a columnar DBMS for OLAP: [https://www.exasol.com/]
> Calcite's current `PostgresqlSqlDialect` works well with Exasol's jdbc
> adapter but there are a few differences (e.g. additional datatypes, some
> calls are slightly different, identifiers, etc.)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
