db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Rick Hillegas (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-4751) Need disable/enable triggers functionality
Date Wed, 21 Jul 2010 12:44:50 GMT

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

Rick Hillegas updated DERBY-4751:
---------------------------------

    Fix Version/s:     (was: 11.0.0.0)
                       (was: 10.6.1.0)
                       (was: 10.7.0.0)
                       (was: 10.6.1.1)

Thanks for logging this enhancement request, Lakshmi. I am unsetting the "Fix Versions" field.
That field is set by the developer who resolves the issue. It lists the release vehicles which
carry the solution--something we don't generally know until someone actually picks up the
issue.

It would be helpful to understand more about how this feature would be used. For instance,
do you need to disable all of the triggers on a table? Do you need to disable individual triggers?

You might want to discuss this issue on the derby-user list. Someone might be able to help
you design a workaround. Thanks.


> Need disable/enable triggers functionality
> ------------------------------------------
>
>                 Key: DERBY-4751
>                 URL: https://issues.apache.org/jira/browse/DERBY-4751
>             Project: Derby
>          Issue Type: Improvement
>    Affects Versions: 10.6.1.0
>            Reporter: Lakshmi Prasanna
>
> It would be good to have functionality for disabling and enabling triggers for a table.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message