db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dag H. Wanvik (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-5794) COMPOUND TRIGGER SUPPORT
Date Fri, 01 Jun 2012 21:37:24 GMT

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

Dag H. Wanvik updated DERBY-5794:
---------------------------------

    Issue Type: Improvement  (was: Bug)

Changed Issue type to Improvement.
                
> 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, 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

        

Mime
View raw message