[
https://issues.apache.org/jira/browse/DERBY-5506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13153618#comment-13153618
]
Knut Anders Hatlen commented on DERBY-5506:
-------------------------------------------
Maybe an example that doesn't use asterisk would be helpful, but I don't think
that example should use multiple columns. Although such queries are allowed
now, I don't think there's any reason why a user would write such a query (more
typing for the exact same behaviour), so there's no reason for us to encourage
it through an example.(The motivation for supporting the syntax was that some
machine-generated SQL contained multiple columns in the EXISTS query.)
I suppose that in addition to removing the above mentioned sentence from the
TableSubquery topic, we should also adjust the preceding sentence to "When used
as a TableExpression in a FROM clause, or with EXISTS, it can return multiple
columns."
> Document that EXISTS subquery can now select more then one column
> -----------------------------------------------------------------
>
> Key: DERBY-5506
> URL: https://issues.apache.org/jira/browse/DERBY-5506
> Project: Derby
> Issue Type: Sub-task
> Components: Documentation
> Reporter: Dag H. Wanvik
> Assignee: Kim Haase
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
