[
https://issues.apache.org/jira/browse/DERBY-2261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12481197
]
Tomohito Nakayama commented on DERBY-2261:
------------------------------------------
I think examples in VALUES expression page shows that we can call it statement
.....
-- 3 rows of 1 column
VALUES (1),(2),(3)
-- 3 rows of 1 column
VALUES 1, 2, 3
-- 1 row of 3 columns
VALUES (1, 2, 3)
-- using a built-in function
VALUES CURRENT_DATE
-- getting the value of an arbitrary expression
VALUES (3*29, 26.0E0/3)
-- getting a value returned by a built-in function
values char(1)
Now I understood that there exists both of VALUES expression and VALUES
statement.
Then I think wording itself is not problem.
// Sorry that my opinion is different from first one ....
However, I think information for VALUES statement is placed too suddenly in
context of VALUES expression page.
Because VALUES statement is not so familiar with many reader, I think some of
care is needed.
> Questionable use of word "statement" in VALUES expression of Derby Reference
> Manual should be changed to "clause"
> -----------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-2261
> URL: https://issues.apache.org/jira/browse/DERBY-2261
> Project: Derby
> Issue Type: Improvement
> Components: Documentation
> Environment:
> http://db.apache.org/derby/docs/dev/ref/rrefsqlj11277.html
> Reporter: Tomohito Nakayama
> Assigned To: Kim Haase
>
> "VALUES statement" in next one sentence in "VALUES expression" of Derby
> Reference manual should be changed to "VALUES clause".
> >You use a VALUES statement when you do not have a FROM clause.
> http://mail-archives.apache.org/mod_mbox/db-derby-dev/200701.mbox/[EMAIL
> PROTECTED]
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
