[
https://issues.apache.org/jira/browse/DERBY-2238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14275237#comment-14275237
]
Kim Haase commented on DERBY-2238:
----------------------------------
Thanks -- this is a good, simple way of fixing the problem. A VALUES expression
is equivalent to a query -- this is stated in the documentation of both the
VALUES expression and a query -- so it's a perfectly valid example. Looks like
the commit has already shown up in the latest alpha manuals, so the issue can
be both resolved and closed.
> Example of ScalarSubquery in Derby Reference Manual is not ScalarSubquery
> --------------------------------------------------------------------------
>
> Key: DERBY-2238
> URL: https://issues.apache.org/jira/browse/DERBY-2238
> Project: Derby
> Issue Type: Bug
> Components: Documentation
> Affects Versions: 10.2.2.0
> Environment:
> http://db.apache.org/derby/docs/dev/ref/rrefscalarsubquery.html
> Reporter: Tomohito Nakayama
> Assignee: Myrna van Lunteren
> Labels: derby_triage10_11
> Attachments: DERBY-2238.diff, DERBY-2238_2.diff,
> rrefscalarsubquery.html, rrefscalarsubquery.html
>
>
> In the page, I found next example.
> -- Introduce a way of "generating" new data values,
> -- using a query which selects from a VALUES clause (which is an
> -- alternate form of a fullselect).
> -- This query shows how a table can be derived called "X" having
> -- 2 columns "R1" and "R2" and 1 row of data.
> SELECT R1,R2
> FROM (VALUES('GROUP 1','GROUP 2')) AS X(R1,R2)
> I think this is not ScalarSubquery because the result have two columns.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
