You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Yip Ng (JIRA)" <de...@db.apache.org> on 2006/10/10 19:24:19 UTC
[jira] Created: (DERBY-1953) Make FOR EACH clause in CREATE TRIGGER
statement optional
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
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
[jira] Updated: (DERBY-1953) Make FOR EACH clause and MODE DB2SQL
in CREATE TRIGGER statement optional
Posted by "Yip Ng (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1953?page=all ]
Yip Ng updated DERBY-1953:
--------------------------
Derby Info: (was: [Patch Available])
> 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
> Affects Versions: 10.2.1.6
> Environment: Any
> Reporter: Yip Ng
> Assigned To: Yip Ng
> Priority: Minor
> Attachments: derby1953-trunk-diff01.txt, derby1953-trunk-diff02.txt, derby1953-trunk-stat01.txt, derby1953-trunk-stat02.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
[jira] Updated: (DERBY-1953) Make FOR EACH clause and MODE DB2SQL
in CREATE TRIGGER statement optional
Posted by "Yip Ng (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1953?page=all ]
Yip Ng updated DERBY-1953:
--------------------------
Attachment: derby1953-trunk-stat04.txt
derby1953-trunk-diff04.txt
Attaching derby1953-trunk-diff04.txt. Previous patch conflicted with DERBY-183 and DERBY-630.
> 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
> Affects Versions: 10.2.1.6
> Environment: Any
> Reporter: Yip Ng
> Assigned To: Yip Ng
> Priority: Minor
> Attachments: 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
[jira] Commented: (DERBY-1953) Make FOR EACH clause and MODE DB2SQL
in CREATE TRIGGER statement optional
Posted by "Yip Ng (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1953?page=comments#action_12441587 ]
Yip Ng commented on DERBY-1953:
-------------------------------
Having problem submitting patch as attachment:
Exception trying to establish attachment directory. Check that the application server and JIRA have permissions to write to it: com.atlassian.jira.web.util.AttachmentException: Cannot write to attachment directory. Check that the application server and JIRA have permissions to write to: /usr/local/tomcat/tomcat-jira/attachments/DERBY/DERBY-1953
> 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
> Affects Versions: 10.2.1.6
> Environment: Any
> Reporter: Yip Ng
> Assigned To: Yip Ng
> Priority: Minor
> Attachments: derby1953-trunk-diff01.txt, derby1953-trunk-diff02.txt, derby1953-trunk-stat01.txt, derby1953-trunk-stat02.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
[jira] Commented: (DERBY-1953) Make FOR EACH clause and MODE DB2SQL
in CREATE TRIGGER statement optional
Posted by "Suresh Thalamati (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1953?page=comments#action_12441312 ]
Suresh Thalamati commented on DERBY-1953:
-----------------------------------------
I reviewed the latest patch , it looks good. I will commit it, after running the tests.
> 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
> Affects Versions: 10.2.1.6
> Environment: Any
> Reporter: Yip Ng
> Assigned To: Yip Ng
> Priority: Minor
> Attachments: derby1953-trunk-diff01.txt, derby1953-trunk-diff02.txt, derby1953-trunk-stat01.txt, derby1953-trunk-stat02.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
[jira] Updated: (DERBY-1953) Make FOR EACH clause and MODE DB2SQL
in CREATE TRIGGER statement optional
Posted by "Yip Ng (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1953?page=all ]
Yip Ng updated DERBY-1953:
--------------------------
Derby Info: [Patch Available]
> 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
> Affects Versions: 10.2.1.6
> Environment: Any
> Reporter: Yip Ng
> Assigned To: Yip Ng
> Priority: Minor
> Attachments: derby1953-trunk-diff01.txt, derby1953-trunk-diff02.txt, derby1953-trunk-diff03.txt, derby1953-trunk-stat01.txt, derby1953-trunk-stat02.txt, derby1953-trunk-stat03.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
[jira] Updated: (DERBY-1953) Make FOR EACH clause and MODE DB2SQL
in CREATE TRIGGER statement optional
Posted by "Yip Ng (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1953?page=all ]
Yip Ng updated DERBY-1953:
--------------------------
Attachment: derby1953-trunk-dita-stat01.txt
derby1953-trunk-dita-diff01.txt
Attaching documentation patch derby1953-trunk-dita-diff01.txt for this jira. The patch updates the ref manual - CREATE TRIGGER syntax and examples. Please review.
> 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-dita-diff01.txt, derby1953-trunk-dita-stat01.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
[jira] Updated: (DERBY-1953) Make FOR EACH clause and MODE DB2SQL
in CREATE TRIGGER statement optional
Posted by "Yip Ng (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1953?page=all ]
Yip Ng updated DERBY-1953:
--------------------------
Affects Version/s: 10.3.0.0
(was: 10.2.1.6)
> 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: Documentation, SQL
> Affects Versions: 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
[jira] Updated: (DERBY-1953) Make FOR EACH clause and MODE DB2SQL
in CREATE TRIGGER statement optional
Posted by "Yip Ng (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1953?page=all ]
Yip Ng updated DERBY-1953:
--------------------------
Affects Version/s: 10.2.1.6
> 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: Documentation, SQL
> 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
[jira] Updated: (DERBY-1953) Make FOR EACH clause and MODE DB2SQL
in CREATE TRIGGER statement optional
Posted by "Yip Ng (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1953?page=all ]
Yip Ng updated DERBY-1953:
--------------------------
Attachment: derby1953-trunk-stat03.txt
derby1953-trunk-diff03.txt
Attaching patch derby1953-trunk-diff03.txt. This patch makes the MODE DB2SQL independent of FOR EACH part. derbyall passes.
> 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
> Affects Versions: 10.2.1.6
> Environment: Any
> Reporter: Yip Ng
> Assigned To: Yip Ng
> Priority: Minor
> Attachments: derby1953-trunk-diff01.txt, derby1953-trunk-diff02.txt, derby1953-trunk-diff03.txt, derby1953-trunk-stat01.txt, derby1953-trunk-stat02.txt, derby1953-trunk-stat03.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
[jira] Updated: (DERBY-1953) Make FOR EACH clause and MODE DB2SQL
in CREATE TRIGGER statement optional
Posted by "Yip Ng (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1953?page=all ]
Yip Ng updated DERBY-1953:
--------------------------
Derby Info: [Patch Available]
> 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-dita-diff01.txt, derby1953-trunk-dita-stat01.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
[jira] Updated: (DERBY-1953) Make FOR EACH clause and MODE DB2SQL
in CREATE TRIGGER statement optional
Posted by "Yip Ng (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1953?page=all ]
Yip Ng updated DERBY-1953:
--------------------------
Derby Info: [Patch Available]
Note that this patch have doc impact on CREATE TRIGGER statement syntax which is described in the ref manual.
> 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
> Affects Versions: 10.2.1.6
> Environment: Any
> Reporter: Yip Ng
> Assigned To: Yip Ng
> Priority: Minor
> Attachments: derby1953-trunk-diff01.txt, derby1953-trunk-diff02.txt, derby1953-trunk-stat01.txt, derby1953-trunk-stat02.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
[jira] Updated: (DERBY-1953) Make FOR EACH clause in CREATE TRIGGER
statement optional
Posted by "Yip Ng (JIRA)" <de...@db.apache.org>.
[ 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
[jira] Updated: (DERBY-1953) Make FOR EACH clause and MODE DB2SQL
in CREATE TRIGGER statement optional
Posted by "Yip Ng (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1953?page=all ]
Yip Ng updated DERBY-1953:
--------------------------
Component/s: Documentation
> 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: Documentation, SQL
> Affects Versions: 10.2.1.6
> Environment: Any
> Reporter: Yip Ng
> Assigned To: Yip Ng
> Priority: Minor
> 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
[jira] Commented: (DERBY-1953) Make FOR EACH clause and MODE DB2SQL
in CREATE TRIGGER statement optional
Posted by "Bernt M. Johnsen (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1953?page=comments#action_12441405 ]
Bernt M. Johnsen commented on DERBY-1953:
-----------------------------------------
Sorry, that was a glitch. The syntax after Yip's patch has been applied will be:
<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
> Affects Versions: 10.2.1.6
> Environment: Any
> Reporter: Yip Ng
> Assigned To: Yip Ng
> Priority: Minor
> Attachments: derby1953-trunk-diff01.txt, derby1953-trunk-diff02.txt, derby1953-trunk-stat01.txt, derby1953-trunk-stat02.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
[jira] Commented: (DERBY-1953) Make FOR EACH clause and MODE DB2SQL
in CREATE TRIGGER statement optional
Posted by "Yip Ng (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1953?page=comments#action_12441491 ]
Yip Ng commented on DERBY-1953:
-------------------------------
Originally, I had MODE DB2SQL to be independent but there is a testcase in db2Compatibility.sql that expects failure when the MODE DB2SQL is specified without the FOR EACH part. That was why I retain the failure with
the current syntax. But after going through the most recent DB2 documentation, it appears that MODE DB2SQL can be optional and independent as well. So I am going to make the correction and change to what Bernt suggested. The syntax is now:
<triggered action> ::=
[ FOR EACH { ROW | STATEMENT } ]
[ MODE DB2SQL ]
<triggered SQL statement>
Need to rerun derbyall. =)
> 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
> Affects Versions: 10.2.1.6
> Environment: Any
> Reporter: Yip Ng
> Assigned To: Yip Ng
> Priority: Minor
> Attachments: derby1953-trunk-diff01.txt, derby1953-trunk-diff02.txt, derby1953-trunk-stat01.txt, derby1953-trunk-stat02.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
[jira] Resolved: (DERBY-1953) Make FOR EACH clause and MODE DB2SQL
in CREATE TRIGGER statement optional
Posted by "Bryan Pendleton (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1953?page=all ]
Bryan Pendleton resolved DERBY-1953.
------------------------------------
Resolution: Fixed
Derby Info: (was: [Patch Available])
Doc patch looks good, Yip, thanks for the patch! I built the doc successfully and viewed
the page and it looks fine. Committed the doc patch to subversion as revision 473979.
> 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: Documentation, SQL
> 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-dita-diff01.txt, derby1953-trunk-dita-stat01.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
[jira] Commented: (DERBY-1953) Make FOR EACH clause and MODE DB2SQL
in CREATE TRIGGER statement optional
Posted by "Suresh Thalamati (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1953?page=comments#action_12442683 ]
Suresh Thalamati commented on DERBY-1953:
-----------------------------------------
Hi Yip ,
Thanks for enhancing the patch , withe Bernt's suggestion. I am not able to apply the patch cleanly, the changes in this patch are conflicting with some other changes (most probably u'r derby-630 fix). Could you please resolve the conflicts and post the patch again.
if there are no further comments from any one else. I will commit the patch.
Thanks
-suresh
> 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
> Affects Versions: 10.2.1.6
> Environment: Any
> Reporter: Yip Ng
> Assigned To: Yip Ng
> Priority: Minor
> Attachments: derby1953-trunk-diff01.txt, derby1953-trunk-diff02.txt, derby1953-trunk-diff03.txt, derby1953-trunk-stat01.txt, derby1953-trunk-stat02.txt, derby1953-trunk-stat03.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
[jira] Updated: (DERBY-1953) Make FOR EACH clause and MODE DB2SQL
in CREATE TRIGGER statement optional
Posted by "Yip Ng (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1953?page=all ]
Yip Ng updated DERBY-1953:
--------------------------
Summary: Make FOR EACH clause and MODE DB2SQL in CREATE TRIGGER statement optional (was: Make FOR EACH clause in CREATE TRIGGER statement optional)
> 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
> 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
[jira] Updated: (DERBY-1953) Make FOR EACH clause and MODE DB2SQL
in CREATE TRIGGER statement optional
Posted by "Yip Ng (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1953?page=all ]
Yip Ng updated DERBY-1953:
--------------------------
Derby Info: (was: [Patch Available])
Unchecking patch available since it is already committed to trunk.
The ref manual needs to be updated with the updated syntax in CREATE TRIGGER 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
> Affects Versions: 10.2.1.6
> Environment: Any
> Reporter: Yip Ng
> Assigned To: Yip Ng
> Priority: Minor
> Attachments: 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
[jira] Commented: (DERBY-1953) Make FOR EACH clause and MODE DB2SQL
in CREATE TRIGGER statement optional
Posted by "Bernt M. Johnsen (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1953?page=comments#action_12441383 ]
Bernt M. Johnsen commented on DERBY-1953:
-----------------------------------------
No, I don't mind ;-) The change for DERBY-1770 is trivial anyway. Two comments though:
1) The standard syntax for <triggered action>:
<triggered action> ::=
[ FOR EACH { ROW | STATEMENT } ]
[ WHEN <left paren> <search condition> <right paren> ]
<triggered SQL statement>
is now in Derby:
<triggered action> ::=
[ FOR EACH { ROW | STATEMENT } [MODE DB2SQL] ]
[ WHEN <left paren> <search condition> <right paren> ]
<triggered SQL statement>
One could have considered
[ FOR EACH { ROW | STATEMENT } ] [MODE DB2SQL]
instead.
If MODE DB2SQL some time in the future ended up with some semantic meaning, it would have been nice to have it independent of the FOR EACH part of the statement. I'm not sure if it natters very much.
2) I was planning to change nearly all tests to go without MODE DB2SQL, and just keep the keywords in db2Compatility.sql. After all, it's harder to get the parser right without these keywords, so that should be the norm in the tests. I'll continue that part of my DERBY-1770 work, since Yip's patch just does some few test extensions.
> 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
> Affects Versions: 10.2.1.6
> Environment: Any
> Reporter: Yip Ng
> Assigned To: Yip Ng
> Priority: Minor
> Attachments: derby1953-trunk-diff01.txt, derby1953-trunk-diff02.txt, derby1953-trunk-stat01.txt, derby1953-trunk-stat02.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
[jira] Updated: (DERBY-1953) Make FOR EACH clause and MODE DB2SQL
in CREATE TRIGGER statement optional
Posted by "Yip Ng (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1953?page=all ]
Yip Ng updated DERBY-1953:
--------------------------
Fix Version/s: 10.3.0.0
> 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: Documentation, SQL
> Affects Versions: 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
[jira] Updated: (DERBY-1953) Make FOR EACH clause in CREATE TRIGGER
statement optional
Posted by "Yip Ng (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1953?page=all ]
Yip Ng updated DERBY-1953:
--------------------------
Derby Info: [Patch Available]
> 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
[jira] Updated: (DERBY-1953) Make FOR EACH clause and MODE DB2SQL
in CREATE TRIGGER statement optional
Posted by "Yip Ng (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1953?page=all ]
Yip Ng updated DERBY-1953:
--------------------------
Attachment: derby1953-trunk-stat02.txt
derby1953-trunk-diff02.txt
Resubmitting patch derby1953-trunk-diff02.txt for DERBY-1953. It is basically the same patch with more testcases. derbyall passes.
> 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
> Affects Versions: 10.2.1.6
> Environment: Any
> Reporter: Yip Ng
> Assigned To: Yip Ng
> Priority: Minor
> Attachments: derby1953-trunk-diff01.txt, derby1953-trunk-diff02.txt, derby1953-trunk-stat01.txt, derby1953-trunk-stat02.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
[jira] Updated: (DERBY-1953) Make FOR EACH clause and MODE DB2SQL
in CREATE TRIGGER statement optional
Posted by "Bernt M. Johnsen (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1953?page=all ]
Bernt M. Johnsen updated DERBY-1953:
------------------------------------
Derby Info: (was: [Patch Available])
Committed revision 469102.
> 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: Documentation, SQL
> Affects Versions: 10.2.1.6
> Environment: Any
> Reporter: Yip Ng
> Assigned To: Yip Ng
> Priority: Minor
> 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
[jira] Commented: (DERBY-1953) Make FOR EACH clause and MODE DB2SQL
in CREATE TRIGGER statement optional
Posted by "Kristian Waagan (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1953?page=comments#action_12441390 ]
Kristian Waagan commented on DERBY-1953:
----------------------------------------
Bernt,
Are you sure the WHEN clause is supported by Derby?
Some time ago I entered DERBY-534, which asks for support for the WHEN clause. I looked up CREATE TRIGGER in the reference manual, but could not find anything about WHEN there.
Do we need to support WHEN to be in compliance with the SQL standard(s)?
If we already support it, the reference manual should be updated and the Jira issue updated.
> 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
> Affects Versions: 10.2.1.6
> Environment: Any
> Reporter: Yip Ng
> Assigned To: Yip Ng
> Priority: Minor
> Attachments: derby1953-trunk-diff01.txt, derby1953-trunk-diff02.txt, derby1953-trunk-stat01.txt, derby1953-trunk-stat02.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
[jira] Commented: (DERBY-1953) Make FOR EACH clause and MODE DB2SQL
in CREATE TRIGGER statement optional
Posted by "Yip Ng (JIRA)" <ji...@apache.org>.
[ 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
[jira] Updated: (DERBY-1953) Make FOR EACH clause and MODE DB2SQL
in CREATE TRIGGER statement optional
Posted by "Yip Ng (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1953?page=all ]
Yip Ng updated DERBY-1953:
--------------------------
Derby Info: (was: [Patch Available])
Found a minor problem with the patch. Unchecking patch available. Will resubmit patch.
> 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
> 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
[jira] Commented: (DERBY-1953) Make FOR EACH clause and MODE DB2SQL
in CREATE TRIGGER statement optional
Posted by "Suresh Thalamati (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1953?page=comments#action_12443000 ]
Suresh Thalamati commented on DERBY-1953:
-----------------------------------------
Committed to trunk , revision 464970. Thanks Yip .
> 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
> Affects Versions: 10.2.1.6
> Environment: Any
> Reporter: Yip Ng
> Assigned To: Yip Ng
> Priority: Minor
> Attachments: 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
[jira] Commented: (DERBY-1953) Make FOR EACH clause and MODE DB2SQL
in CREATE TRIGGER statement optional
Posted by "Yip Ng (JIRA)" <de...@db.apache.org>.
[ http://issues.apache.org/jira/browse/DERBY-1953?page=comments#action_12443010 ]
Yip Ng commented on DERBY-1953:
-------------------------------
Thanks Suresh, Bernt and Kristian for the review.
> 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
> Affects Versions: 10.2.1.6
> Environment: Any
> Reporter: Yip Ng
> Assigned To: Yip Ng
> Priority: Minor
> Attachments: 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