Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 63311 invoked from network); 3 May 2010 14:17:22 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 3 May 2010 14:17:22 -0000 Received: (qmail 59994 invoked by uid 500); 3 May 2010 14:17:22 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 59965 invoked by uid 500); 3 May 2010 14:17:22 -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 59958 invoked by uid 99); 3 May 2010 14:17:22 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 May 2010 14:17:22 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.22] (HELO thor.apache.org) (140.211.11.22) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 03 May 2010 14:17:20 +0000 Received: from thor (localhost [127.0.0.1]) by thor.apache.org (8.13.8+Sun/8.13.8) with ESMTP id o43EGwxH025272 for ; Mon, 3 May 2010 14:16:58 GMT Message-ID: <28442258.14151272896218362.JavaMail.jira@thor> Date: Mon, 3 May 2010 10:16:58 -0400 (EDT) From: "Knut Anders Hatlen (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-4610) Error attempting delete with cascade and triggers In-Reply-To: <1441724085.5801270816190773.JavaMail.jira@brutus.apache.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 X-Virus-Checked: Checked by ClamAV on apache.org [ https://issues.apache.org/jira/browse/DERBY-4610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12863358#action_12863358 ] Knut Anders Hatlen commented on DERBY-4610: ------------------------------------------- I reverse merged the commits from DERBY-3049 for now and committed revision 940462. If we find a safe way to add those changes, we can always reintroduce them later. I'll look into back-porting to 10.6 in a couple of days if there are no problems in the nightly tests. > Error attempting delete with cascade and triggers > ------------------------------------------------- > > Key: DERBY-4610 > URL: https://issues.apache.org/jira/browse/DERBY-4610 > Project: Derby > Issue Type: Bug > Components: SQL > Affects Versions: 10.4.1.3, 10.4.2.0, 10.5.3.0, 10.6.1.0 > Environment: Apache Derby 10.5.3.0 and Sun JDK 1.6.0_07 > Reporter: Eric Long > Attachments: junit.diff > > > The scenario is a parent and child table with a cascade delete and triggers on both tables. Here are the steps to reproduce. > First, compile TestFunctions.java and put it on the classpath: > public class TestFunctions > { > public static void test(String str) > { > } > } > Next, enter commands into interactive SQL: > create table testtable (id integer, name varchar(20), primary key(id)); > create table testchild ( > id integer > constraint fk_id references testtable on delete cascade, > ordernum int, > primary key(id)); > create procedure testproc (str varchar(20)) > PARAMETER STYLE JAVA LANGUAGE JAVA EXTERNAL NAME 'TestFunctions.test'; > create trigger testtabletrigger after delete on testtable referencing old as old > for each row mode db2sql call testproc(char(old.id)); > create trigger testchildtrigger after delete on testchild referencing old as old > for each row mode db2sql call testproc(char(old.ordernum)); > insert into testtable values (1, 'test1'); > insert into testchild values (1, 10); > delete from testtable where id = 1; > The expected result is that deleting a row from "testtable" will cascade the delete to "testchild", and the triggers will be called for each delete. The actual result is that the delete is rolled back with the following error: > Error: An attempt was made to put a data value of type 'java.lang.String' into a data value of > type 'INTEGER'. > SQLState: XCL12 > ErrorCode: 30000 > There are no additional entries in the derby.log after the error. If only one trigger is used, or if the cascade is removed, then the delete will succeed. > This issue was found while using SymmetricDS, which uses triggers to replicate tables between Derby databases. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.