db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Suresh Thalamati (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1953) Make FOR EACH clause and MODE DB2SQL in CREATE TRIGGER statement optional
Date Tue, 10 Oct 2006 23:09:20 GMT
    [ 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

        

Mime
View raw message