db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1953) Make FOR EACH clause and MODE DB2SQL in CREATE TRIGGER statement optional
Date Wed, 11 Oct 2006 09:52:20 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1953?page=comments#action_12441390 ] 
Kristian Waagan commented on DERBY-1953:


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:
>         Environment: Any
>            Reporter: Yip Ng
>         Assigned To: Yip Ng
>            Priority: Minor
>         Attachments: derby1953-trunk-diff01.txt, derby1953-trunk-diff02.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.

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