[
https://issues.apache.org/jira/browse/DERBY-5121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13013858#comment-13013858
]
Mamta A. Satoor commented on DERBY-5121:
----------------------------------------
I do not forsee any further code changes related to backing out DERBY-1482
changes so I think it should be safe to resolve this issue so we don't have any
blockers for 10.8 release.
The right fix for DERBY-1482 can go in as part of DERBY-1482 even after 10.8
release is out. Those changes can then be made available as next point release
of 10.8 and since at the time of upgrade, the trigger SPSes get marked invalid,
any changes made for DERBY-1482 will get automatically picked up.
> 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, Test_5121_Upgrade.java,
> derby-5121-01-aa-runTimeRemapping.diff, derby5121_patch1_diff.txt,
> releaseNote.html, 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
