[
https://issues.apache.org/jira/browse/CALCITE-992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15039759#comment-15039759
]
Julian Hyde commented on CALCITE-992:
-------------------------------------
[~maryannxue], I created a branch
https://github.com/julianhyde/calcite/tree/992-validate-seq with your change,
then I made my own change, backing out some of your edits and adding my own.
You'll see that I don't pass the sequence table object but instead pass its
unique name (a list of strings, converted temporarily into a single string like
{{"schema"."table"}}. That string can be converted to a string list, then used
to get a RelOptTable inside the code that implements the sequence function by
generating java code. Hopefully that's what you need.
> Validate and resolve sequence reference as a Table object
> ---------------------------------------------------------
>
> Key: CALCITE-992
> URL: https://issues.apache.org/jira/browse/CALCITE-992
> Project: Calcite
> Issue Type: Sub-task
> Reporter: Maryann Xue
> Assignee: Maryann Xue
> Fix For: 1.6.0
>
> Attachments: CALCITE-992.suggested.diff
>
>
> Currently the validator does not validate if the sequence exists or if the
> corresponding table is of the required type, etc. Also, in NEXT_VALUE and
> CURRENT_VALUE function, we need the sequence Table object instead of the
> sequence name string.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
