[
https://issues.apache.org/jira/browse/CALCITE-1913?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16109555#comment-16109555
]
Jess Balint commented on CALCITE-1913:
--------------------------------------
You could argue the same for exposing the DB product from the {{SqlDialect}}.
The low-level details are exposed for others - whether it's a CALCITE-1841
{{Handler}}, or other (3rd party) code - to build those abstractions. This
doesn't prevent us from adding more methods to a dialect to determine behavior
(e.g. the existing {{supportsOffsetFetch()}}, {{allowsAs()}},
{{requiresAliasForFromItems()}}, etc).
> Include DB version in SqlDialect
> --------------------------------
>
> Key: CALCITE-1913
> URL: https://issues.apache.org/jira/browse/CALCITE-1913
> Project: Calcite
> Issue Type: Improvement
> Components: core
> Affects Versions: 1.13.0
> Reporter: Jess Balint
> Assignee: Jess Balint
> Priority: Minor
> Fix For: 1.14.0
>
>
> It would be useful to have the DB version # in the SqlDialect for unparsing
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
