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] Created: (DERBY-3940) Dropping a column does not drop triggers which mention that column
Date Fri, 07 Nov 2008 14:06:44 GMT
Dropping a column does not drop triggers which mention that column
------------------------------------------------------------------

                 Key: DERBY-3940
                 URL: https://issues.apache.org/jira/browse/DERBY-3940
             Project: Derby
          Issue Type: Bug
          Components: SQL
    Affects Versions: 10.4.2.1, 10.5.0.0
            Reporter: Rick Hillegas


Put an INSERT trigger on a table and mention a column in the trigger. Then drop that column
from the table. If you drop the column with RESTRICT semantics, you don't get an objection.
Both CASCADE and RESTRICT drop the column. However, the trigger remains in both cases. After
that, INSERTs into the table fail because the trigger can't find the dropped column. The workaround
is to manually drop the trigger either before or after dropping the column. I will attach
a test case.

-- 
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