[
https://issues.apache.org/jira/browse/DERBY-6383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamta A. Satoor updated DERBY-6383:
-----------------------------------
Attachment: derby_for_Embedded_40Changes10_7testTriggers.log
derby_for_Embedded_40Changes10_9testDisposableStatisticsExplicit.log
error-stacktrace_for_Embedded_40Changes10_9testDisposableStatisticsExplicit.out
error-stacktrace_for_Embedded_40Changes10_7testTriggers.out
runall.out
DERBY6383_patch2_diff.txt
Knut, thanks so much for reviewing the patch.
I am attaching a new patch DERBY6383_patch2_diff.txt(which is not ready for
commit). It takes care of Knut's comment and adds a junit test and adds an
upgrade test. I am having problems with the upgrade tests and am wondering if
the failure rings a bell to anyone. Basically, the junit tests(suites.All which
includes upgrade suite)works perfectly fine with my patch **if I disable the
newly added upgrade suite in the attached patch**. But if I include my new
upgrade fixture in the upgrade suite and run suites.All, I am getting errors
similar to DERBY-5947 and DERBY-6203. Further more, some other upgrade tests
fail after them but it may be the side effects of the failures seen by
DERBY-5947 and DERBY-6203. I am attaching the output of the stand alone upgrade
suite(upgradeTests._Suite) run for reference(this upgrade suite was run with my
newly added upgrade test in the patch) as runall.out. Additionally, I have also
attached error-stacktrace and derby.log for testTriggers and
testDisposableStatisticsExplicit.
I will try to narrow down the releases that we include for upgrade suite to see
if I can have a shorter upgrade suite to share which runs into the problems I
am experiencing. Appreciate all the help. Thanks.
> Update trigger defined on one column fires on update of other columns
> ---------------------------------------------------------------------
>
> Key: DERBY-6383
> URL: https://issues.apache.org/jira/browse/DERBY-6383
> Project: Derby
> Issue Type: Bug
> Components: SQL
> Affects Versions: 10.7.1.4, 10.8.1.2, 10.9.1.0, 10.10.1.1
> Reporter: Knut Anders Hatlen
> Assignee: Mamta A. Satoor
> Attachments: d6383.sql, DERBY6383_patch1_diff.txt,
> DERBY6383_patch2_diff.txt, derby_for_Embedded_40Changes10_7testTriggers.log,
> derby_for_Embedded_40Changes10_9testDisposableStatisticsExplicit.log,
> error-stacktrace_for_Embedded_40Changes10_7testTriggers.out,
> error-stacktrace_for_Embedded_40Changes10_9testDisposableStatisticsExplicit.out,
> runall.out
>
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
