db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Matrigali (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5121) Data corruption when executing an UPDATE trigger
Date Mon, 21 Mar 2011 23:01:06 GMT

    [ https://issues.apache.org/jira/browse/DERBY-5121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13009459#comment-13009459
] 

Mike Matrigali commented on DERBY-5121:
---------------------------------------

Are you still planning on first backporting the fix made to 10.7 into the trunk line?  Have
you done any more work to determine if the out of memory is this change or something in your
environment?    Given the issues we have had with triggers it may make more sense to go with
the safe change for 10.8 and then later after 10.8 is cut you can check in your new fix to
trunk and get testing there before putting it into a released codeline.

My interpretation of reviewing the change is that it should be safe and not cause unexpected
out of memory.  It is basically just
making all code go through the existing code path that all pre 10.7 databases are already
executing.

If you are uncomfortable with your current testing maybe you could post the exact patch against
trunk that you are trying and someone else can run tests based on it.


> 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

Mime
View raw message