Details
Description
I see this problem on 10.8 and higher. To reproduce, create a database with a trigger like this:
connect 'jdbc:derby:trigdb;create=true';
create table t1(x int, y int);
create table t2(x int, y int);
create trigger tr after update of x on t1 referencing old table as old insert into t2 select * from old;
Then run dblook on the database, and you'll see the following output:
– ----------------------------------------------
– DDL Statements for triggers
– ----------------------------------------------
CREATE TRIGGER "APP"."TR" AFTER UPDATE OF "X", "Y" ON "APP"."T1" REFERENCING OLD_TABLE AS OLD FOR EACH STATEMENT insert into t2 select * from old;
Notice that the DDL creates an update trigger for columns X and Y, whereas the original trigger was defined on column X only.
I see the expected DDL on 10.7.1.1.
Attachments
Attachments
Issue Links
- breaks
-
DERBY-6547 testDERBY5120NumRowsInSydependsForTrigger fails when the starting version of the upgrade trajectory is 10.10.2.0
- Closed
- is broken by
-
DERBY-4874 Trigger does not recognize new size of VARCHAR column expanded with ALTER TABLE. It fails with ERROR 22001: A truncation error was encountered trying to shrink VARCHAR
- Closed
- is related to
-
DERBY-6417 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.".
- Open
- relates to
-
DERBY-6684 Failure in testDERBY5120NumRowsInSydependsForTrigger when upgrading from 10.11.1.0 to trunk
- Closed