[jira] [Commented] (CALCITE-1523) Add RelBuilder field() method to reference aliased relations not on top of stack
[ https://issues.apache.org/jira/browse/CALCITE-1523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15713734#comment-15713734 ] Julian Hyde commented on CALCITE-1523: -- Yes, I think that would be useful. But if we allow null alias names (I don't remember) we should continue to allow that. > Add RelBuilder field() method to reference aliased relations not on top of > stack > > > Key: CALCITE-1523 > URL: https://issues.apache.org/jira/browse/CALCITE-1523 > Project: Calcite > Issue Type: Improvement > Components: core >Reporter: Jess Balint >Assignee: Julian Hyde >Priority: Minor > > It would be convenient to reference aliased tables that are not on top of the > RelBuilder stack. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (CALCITE-1523) Add RelBuilder field() method to reference aliased relations not on top of stack
[ https://issues.apache.org/jira/browse/CALCITE-1523?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15713502#comment-15713502 ] Jess Balint commented on CALCITE-1523: -- I don't see anything preventing conflicting alias names. should this be validated in the {{Frame}} constructor? > Add RelBuilder field() method to reference aliased relations not on top of > stack > > > Key: CALCITE-1523 > URL: https://issues.apache.org/jira/browse/CALCITE-1523 > Project: Calcite > Issue Type: Improvement > Components: core >Reporter: Jess Balint >Assignee: Julian Hyde >Priority: Minor > > It would be convenient to reference aliased tables that are not on top of the > RelBuilder stack. -- This message was sent by Atlassian JIRA (v6.3.4#6332)