[
https://issues.apache.org/jira/browse/DERBY-4399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12780179#action_12780179
]
Dag H. Wanvik commented on DERBY-4399:
--------------------------------------
Thanks for picking this one up, Kim. I think it's ok to use the existing topic.
I suggest renaming "correlation" to "correlation clause", and present the
syntax in the (renamed) topic, but not give any specific definition to that
term (a clause is a grammar entity); just keep the current explanation for
correlation-name.
> Syntax description for TableViewOrFunctionExpression lack subquery option
> -------------------------------------------------------------------------
>
> Key: DERBY-4399
> URL: https://issues.apache.org/jira/browse/DERBY-4399
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Reporter: Dag H. Wanvik
> Assignee: Kim Haase
>
> In the reference manual, we find these syntax descriptions (start with
> http://db.apache.org/derby/docs/dev/ref/rrefsqlj21583.html):
> TableExpression:
> {
> TableViewOrFunctionExpression | JOIN operation
> }
> TableViewOrFunctionExpression:
> { table-Name | view-Name | TableFunctionInvocation}
> [ [ AS ] correlation-Name
> [ (Simple-column-Name [ , Simple-column-Name]* ) ] ] ]
> I cannot find a way from the "FROM clause" to the TableSubquery production,
> so I think the latter should read:
> { table-Name | TableSubquery | view-Name | TableFunctionInvocation }
> [ [ AS ] correlation-Name
> [ (Simple-column-Name [ , Simple-column-Name]* ) ] ] ]
> Also, the "JOIN operation" is not clickable.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
