Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Wed, 30 Mar 2011 09:56:06 +0000 (UTC)
From: "Mamta A. Satoor (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: 
 <1872252940.21037.1301478966587.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <2006077621.9928.1299724919420.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (DERBY-5121) Data corruption when executing an
 UPDATE trigger
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


     [ https://issues.apache.org/jira/browse/DERBY-5121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mamta A. Satoor updated DERBY-5121:
-----------------------------------

    Attachment: DERBY_5121_NotReadForCommit_patch4_trunk_diff.txt

I have spent some time analyzing the changes that went into UpdateNode as part of DERBY-1482 and I believe that the attached patch, DERBY_5121_NotReadForCommit_patch4_trunk_diff.txt, does the correct job of undoing those changes from UpdateNode. The patch I attached on March 29th(DERBY_5121_NotReadForCommit_patche_trunk_diff.txt) did not remove those changes properly.

I have also written an upgrade case testing the behavior of UPDATE reading correct columns from the trigger table so that trigger finds the columns it needs.

I am running junit suite right now to make sure nothing breaks with the attached patch. will also run derbyall suite once junit is finished successfully.

> Data corruption when executing an UPDATE trigger
> ------------------------------------------------
>
>                 Key: DERBY-5121
>                 URL: https://issues.apache.org/jira/browse/DERBY-5121
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 10.7.1.1, 10.8.0.0
>            Reporter: Rick Hillegas
>            Assignee: Mamta A. Satoor
>              Labels: derby_triage10_8
>         Attachments: 5121_create.sql, 5121_upgrade.sql, DERBY_5121_NotReadForCommit_patch3_trunk_diff.txt, DERBY_5121_NotReadForCommit_patch4_trunk_diff.txt, DERBY_5121_backoutDerby1492_changes_patch3_trunk_diff.txt, DERBY_5121_patch2_trunk_diff.txt, DummyProc.java, Proc_5121.java, Test_5121.java, derby-5121-01-aa-runTimeRemapping.diff, derby5121_patch1_diff.txt, releaseNote.html, triggerBug.sql, triggerBug.sql, triggeredBug2.sql, triggeredCorruption.sql
>
>
> When executing an UPDATE trigger, the following error is raised. I will attach a test case:
> ERROR XCL12: An attempt was made to put a data value of type 'org.apache.derby.impl.jdbc.EmbedClob' into a data value of type 'INTEGER'.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira