You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Maryann Xue (JIRA)" <ji...@apache.org> on 2015/12/02 03:05:10 UTC
[jira] [Updated] (CALCITE-992) Validate and resolve sequence
reference as a Table object
[ https://issues.apache.org/jira/browse/CALCITE-992?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maryann Xue updated CALCITE-992:
--------------------------------
Attachment: CALCITE-992.suggested.diff
I managed to put together the validation and sequence resolving stuff, but had a little problem with making the RelOptTable a RexLiteral. The current patch looks a bit ugly since the changes get everywhere in order to make RexLiteral enclose this RelOptTable object. An alternative I'm thinking is to create a new RexNode type, say, RexTableReference (or RexSequenceReference). Any suggestions, [~julianhyde]?
> 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)