[
https://issues.apache.org/jira/browse/DERBY-5121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009736#comment-13009736
]
Mike Matrigali commented on DERBY-5121:
---------------------------------------
I believe the tests that you see failing in your run were written specifically
to test
DERBY-1482. In order to test that blobs are not being read into memory the
tests specifically are coded
to read blobs into memory in the cases that DERBY-1482 fixes. It is ASSUMED
that in the normal suite run
that there will be enough memory for the tests to pass, and that when the same
tests are run as part of the
"small memory" test suite that the bugs will be caught. But maybe due to
timing, machine resources, or
previous tests run these tests no longer successfully run guaranteed in default
suite run on trunk. It would
seem like disabling DERBY-1482 should also disable the memory specific tests if
we think those tests are
not valid once the feature is disabled.
> 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_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
