[
https://issues.apache.org/jira/browse/DERBY-6417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamta A. Satoor updated DERBY-6417:
-----------------------------------
Fix Version/s: 10.11.0.0
10.10.1.3
10.9.2.2
10.8.3.1
I have not researched what jira/commit has fixed the behavior in 10.8 and
higher releases.
> Dropping a column in 10.7 release when there is a trigger with REFERENCING
> OLD clause defined on the table gives error "ERROR 42X05: Table/View 'OLD'
> does not exist.".
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DERBY-6417
> URL: https://issues.apache.org/jira/browse/DERBY-6417
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.7.1.4
> Reporter: Mamta A. Satoor
> Fix For: 10.8.3.1, 10.9.2.2, 10.10.1.3, 10.11.0.0
>
>
> While working on DERBY-6383, wrote a junit test case to test the impact of
> DROP COLUMN on the triggers, found following incorrect behavior with 10.7
> release. The behavior is correct on 10.8 and higher releases
> CREATE TABLE DERBY_6368_TAB1 (X INTEGER, Y INTEGER);
> CREATE TABLE DERBY_6368_TAB2 (X INTEGER, Y INTEGER);
> INSERT INTO DERBY_6368_TAB1 VALUES(1, 2);
> CREATE TRIGGER t3 AFTER UPDATE ON DERBY_6368_TAB1 REFERENCING old table AS
> old INSERT INTO DERBY_6368_TAB2 SELECT * FROM old;
> --1 row
> UPDATE DERBY_6368_TAB1 SET x = x + 1;
> select count(*) from DERBY_6368_TAB2;
> ALTER TABLE DERBY_6368_TAB1 DROP COLUMN Y;
> The ALTER TABLE above gives correct warning in 10.8 and higher as shown below
> WARNING 01502: The trigger T3 on table DERBY_6368_TAB1 has been dropped.
> but 10.7 gives following error
> ERROR 42X05: Table/View 'OLD' does not exist.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
