[
https://issues.apache.org/jira/browse/DERBY-5794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13286606#comment-13286606
]
Rick Hillegas commented on DERBY-5794:
--------------------------------------
Compound triggers appear to be an Oracle-specific extension. They do not appear
in the SQL Standard. If we added a corresponding extension to Derby, we would
probably want to use Derby-specific syntax which would be designed to not
conflict with future revs of the SQL Standard. We are generally very cautious
about adding non-standard syntax unless there is significant demand for it.
> COMPOUND TRIGGER SUPPORT
> ------------------------
>
> Key: DERBY-5794
> URL: https://issues.apache.org/jira/browse/DERBY-5794
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.8.1.2
> Reporter: Chirag Mehta
> Priority: Minor
> Labels: compound, performance, simplex, trigger
>
> I tried to search the for support of Compound Triggers like Oracle, didn't
> found any support in Derby 10.8 may be this would be a good functionality we
> can support. I really like using derby, this is my first project where I
> start using derby as an interim database for developers. We have oracle in
> production. So if we have compund trigger support with derby it would be grt.
> Write now as workaround I am creating 3 triggers (After insert, update and
> delete) in derby and 1 in oracle.
> If we have compound trigger it would increase the performance also.
> Thanks a ton team for your work
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
