[
https://issues.apache.org/jira/browse/DERBY-5121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-5121:
---------------------------------
Summary: Problem mapping the update row to the row passed to the action
statement when executing an UPDATE trigger (was: Problem mapping column to
procedure arg when executing an UPDATE trigger)
Changing the description of this bug since experiments show that it is more
general. The triggered action seems to expect a row which just contains the
columns necessary to execute the action. However, if the UPDATE touches columns
which aren't mentioned by the trigger, those columns turn up in the row passed
to the action. These extra columns can be in the middle of the action row. This
throws off the column number of the compiled action and springs this bug.
> Problem mapping the update row to the row passed to the action statement 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
>
>
> 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
