[ http://issues.apache.org/jira/browse/DERBY-1953?page=all ]
Yip Ng updated DERBY-1953:
--------------------------
Attachment: derby1953-trunk-stat01.txt
derby1953-trunk-diff01.txt
Attaching patch derby1953-trunk-diff01.txt. This patch makes the FOR EACH
clause optional in CREATE TRIGGER statement. Since the changes are mainly in
the trigger definition of sqlgrammar.jj file and to make this backward
compatibile with previous releases of Derby, I also addressed DERBY-1770, Make
MODE DB2SQL optional. (Hope Bernt doesn't mind) derbylang passes. Running
derbyall now.
> Make FOR EACH clause in CREATE TRIGGER statement optional
> ---------------------------------------------------------
>
> Key: DERBY-1953
> URL: http://issues.apache.org/jira/browse/DERBY-1953
> Project: Derby
> Issue Type: Improvement
> Components: SQL
> Affects Versions: 10.2.1.6
> Environment: Any
> Reporter: Yip Ng
> Assigned To: Yip Ng
> Priority: Minor
> Attachments: derby1953-trunk-diff01.txt, derby1953-trunk-stat01.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
