[
https://issues.apache.org/jira/browse/DERBY-5121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mamta A. Satoor updated DERBY-5121:
-----------------------------------
Attachment: DERBY_5121_backoutDerby1492_changes_patch3_trunk_diff.txt
I am attaching a new patch
(DERBY_5121_backoutDerby1492_changes_patch3_trunk_diff.txt) for trunk which
will backport DERBY-1482 changes from trunk, same as 10.7 and will do some
additional work(this patch has additional changes than
DERBY_5121_patch2_trunk_diff.txt).
The patch will also disable the tests that were added for DERBY-1482.
With DERBY-1482, these tests would not read in large object columns into memory
because the triggers didn't need them. But now that DERBY-1482 changes are
being backed out, the large object columns will be read in which can cause the
test to run out of memory depending on how much heap is available to it.
I am running the junit suite just one more time to make sure that I don't run
into any OOMs. Once the junit tests run fine, I will go ahead and commit this
patch to trunk, thus backing out DERBY-1482 changes.
The patch also has a comment in DataDictionaryImpl:getTriggerActionString
explaining the code changes for backout. I will add that comment in 10.7 too.
Once the tests run fine on trunk, I will disable DERBY-1482 tests on 10.7 too.
If any comments, please feel free to post them.
> 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:
> DERBY_5121_backoutDerby1492_changes_patch3_trunk_diff.txt,
> DERBY_5121_patch2_trunk_diff.txt, DummyProc.java, Test_5121.java,
> derby-5121-01-aa-runTimeRemapping.diff, 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
