[ 
https://issues.apache.org/jira/browse/CALCITE-1940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16152786#comment-16152786
 ] 

Julian Hyde commented on CALCITE-1940:
--------------------------------------

I'm not fond of introducing sub-classes of RexCall because there is a lot of 
code that wouldn't know how to handle them. But in this case it seems to be the 
least bad option.

This PR is converging, but not fast enough to make it into 1.14. Let's aim to 
get this done for 1.15.

With 71 files changed, the PR is *much* larger than I expected. It seems that 
there are changes to the life-cycle of dialects and handlers. I will need to 
understand whether those changes are necessary or at least beneficial. I am on 
vacation until tomorrow but will review again when I get back.

> 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)

Reply via email to