[
https://issues.apache.org/jira/browse/CALCITE-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16151573#comment-16151573
]
Christian Beikov commented on CALCITE-1940:
-------------------------------------------
I introduced a custom RexCall subclass since I need to store the RelNode
representing the sequence table, but now I'd need to enforce the usage of the
"correct" plan. Currently the optimizer generates plans that use the linq4j
implementation which is "wrong". Maybe you could take a look at the PR and tell
me how to do that best?
> 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)
