[
https://issues.apache.org/jira/browse/CALCITE-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16151561#comment-16151561
]
Christian Beikov commented on CALCITE-1940:
-------------------------------------------
Ok I understand how that works now, I was just confused because the SQL string
was generated(apparently for no reason?) within the Prepare class. Anyway, I'm
having a different problem now with the sequence implementation. The plan looks
like {{LogicalProject(NEXT VALUE FOR S2) -> LogicalValues( (0) )}} and during
rule registration, no JDBC rules are registered since there is no JDBC relation
used in RelNode. Any hints on how I can achieve that the plan gets converted to
{{JdbcProject(NEXT VALUE FOR S2) -> JdbcValues( (0) )}}?
> 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)
