[
https://issues.apache.org/jira/browse/DERBY-5121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-5121:
---------------------------------
Bug behavior facts: [Data corruption, Regression, Seen in production]
(was: [Seen in production])
Summary: Data corruption when executing an UPDATE trigger (was:
Problem mapping the update row to the row passed to the action statement when
executing an UPDATE trigger)
It turns out that this bug can manifest itself as data corruptions. I will
attach a repro showing that. The bug does not appear in 10.6.2.1 but it does
appear in 10.7.1.1. Changing the title of this issue and marking it as a data
corrupting regression.
> 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
> Labels: derby_triage10_8
> Attachments: DummyProc.java, triggerBug.sql, triggerBug.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
