[
https://issues.apache.org/jira/browse/DERBY-5121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rick Hillegas updated DERBY-5121:
---------------------------------
Attachment: Test_5121.java
Attaching Test_5121.java. This test exhaustively walks through all subsets and
permutations of columns for a trigger which inserts into a side table based on
updates to a master table. The test runs cleanly with Mamta's patch applied. I
think this will be a good acceptance test for the solution. Here is how you run
this test:
Usage:
java Test_5121 connectionURL columnCount debug
where
connectionURL is the url to the database
columnCount is the number of columns in the triggering table
debug indicates whether to print out extra debug information
E.g.:
java Test_5121 "jdbc:derby:memory:db;create=true" 3 false
> 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: DummyProc.java, Test_5121.java,
> derby5121_patch1_diff.txt, 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
