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 "Kathey Marsden (JIRA)" <ji...@apache.org> on 2015/10/16 19:38:05 UTC

[jira] [Updated] (DERBY-5794) COMPOUND TRIGGER SUPPORT

     [ https://issues.apache.org/jira/browse/DERBY-5794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kathey Marsden updated DERBY-5794:
----------------------------------
    Issue & fix info:   (was: Newcomer)

> COMPOUND TRIGGER SUPPORT
> ------------------------
>
>                 Key: DERBY-5794
>                 URL: https://issues.apache.org/jira/browse/DERBY-5794
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 10.8.1.2
>            Reporter: Chirag Mehta
>            Priority: Minor
>              Labels: compound, derby_triage10_10, 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 was sent by Atlassian JIRA
(v6.3.4#6332)