[
http://issues.apache.org/jira/browse/DERBY-1953?page=comments#action_12448830 ]
Yip Ng commented on DERBY-1953:
-------------------------------
I think this issue can be marked as resolved once the ref manual
documentation's CREATE TRIGGER syntax is updated.
<triggered action> ::=
[ FOR EACH { ROW | STATEMENT } ]
[ MODE DB2SQL ]
<triggered SQL statement>
> Make FOR EACH clause and MODE DB2SQL in CREATE TRIGGER statement optional
> -------------------------------------------------------------------------
>
> Key: DERBY-1953
> URL: http://issues.apache.org/jira/browse/DERBY-1953
> Project: Derby
> Issue Type: Improvement
> Components: SQL, Documentation
> Affects Versions: 10.2.1.6, 10.3.0.0
> Environment: Any
> Reporter: Yip Ng
> Assigned To: Yip Ng
> Priority: Minor
> Fix For: 10.3.0.0
>
> Attachments: derby-1770-tests-v2.diff, derby-1770-tests-v2.stat,
> derby-1770-tests.diff, derby-1770-tests.stat, derby1953-trunk-diff01.txt,
> derby1953-trunk-diff02.txt, derby1953-trunk-diff03.txt,
> derby1953-trunk-diff04.txt, derby1953-trunk-stat01.txt,
> derby1953-trunk-stat02.txt, derby1953-trunk-stat03.txt,
> derby1953-trunk-stat04.txt
>
>
> According to SQL:2003 standard, section 11.39 <trigger definition>, under
> Syntax Rules item 8:
> If neither FOR EACH ROW nor FOR EACH STATEMENT is specified, then FOR EACH
> STATEMENT is implicit.
> [ FOR EACH { ROW | STATEMENT } ]
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
