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 Mon, 16 Oct 2006 19:40:38 GMT
    [ 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. 


> 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:
>         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.

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


View raw message