Return-Path: X-Original-To: apmail-db-derby-dev-archive@www.apache.org Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1D1A210E25 for ; Tue, 12 Nov 2013 17:17:24 +0000 (UTC) Received: (qmail 15453 invoked by uid 500); 12 Nov 2013 17:17:23 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 15202 invoked by uid 500); 12 Nov 2013 17:17:20 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 15099 invoked by uid 99); 12 Nov 2013 17:17:19 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Nov 2013 17:17:19 +0000 Date: Tue, 12 Nov 2013 17:17:19 +0000 (UTC) From: "Mamta A. Satoor (JIRA)" To: derby-dev@db.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (DERBY-6383) Update trigger defined on one column fires on update of other columns MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DERBY-6383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Mamta A. Satoor updated DERBY-6383: ----------------------------------- Fix Version/s: 10.7.1.4 > 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 > Fix For: 10.7.1.4, 10.8.3.1, 10.9.2.2, 10.10.1.3, 10.11.0.0 > > Attachments: DERBY6383_patch1_diff.txt, DERBY6383_patch2_diff.txt, DERBY6383_patch3_diff.txt, d6383.sql, 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, releaseNote.html, releaseNote.html, 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)