[
https://issues.apache.org/jira/browse/DERBY-5121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012952#comment-13012952
]
Rick Hillegas commented on DERBY-5121:
--------------------------------------
Thanks, Mamta. I have verified that the production problem goes away if I apply
DERBY_5121_NotReadForCommit_patch4_trunk_diff.txt. Thanks.
> 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
