[
https://issues.apache.org/jira/browse/CALCITE-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16148807#comment-16148807
]
Christian Beikov commented on CALCITE-1940:
-------------------------------------------
I need the dialect since I have to call the unparse method on it. If we have a
query like e.g. "select next value for s1.seq, next value for s2.seq" and s1
and s2 are schemas that have different dialects, I have to unparse the sequence
call once for the dialect of s1 and once for s2. I somehow need to know in the
{{SqlWriter}} which dialect a schema uses so that I can call the appropriate
unparse method.
Could you([~chris-baynes]) maybe comment on the mailing list thread
"JdbcAdapter Sort Limit and Offset" which is somewhat related in the overall
discussion about how to handle the different dialect quirks. I'd like to
essentially merge the {{Handler}} and other methods into a DBMS specific
{{SqlDialect}} implementation and do the dialect construction through a
configurable factory.
> Implement dialect specific support for sequences
> ------------------------------------------------
>
> Key: CALCITE-1940
> URL: https://issues.apache.org/jira/browse/CALCITE-1940
> Project: Calcite
> Issue Type: Improvement
> Reporter: Christian Beikov
> Assignee: Julian Hyde
>
> The Calcite parser and validator already supports sequences but the push down
> to the JDBC level is currently limited. SInce sequences are not supported on
> all DBMS every sql dialect should have the possibility to render it's own way
> of extracting sequence information or incrementing the value.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
