db-derby-dev mailing list archives

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

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

Rick Hillegas commented on DERBY-5121:
--------------------------------------

Through binary search I have identified the checkin which introduced this data corruption:

r956763 | mamta | 2010-06-21 19:41:48 -0700 (Mon, 21 Jun 2010) | 5 lines

DERBY-1482

Only read the needed columns for the update trigger when create trigger has identified the
columns which will be used in trigger action through the REFERENCING clause. This will avoid
reading columns that are not needed thus avoiding OOM problems if the underlying table has
large LOBs.


> 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
>              Labels: derby_triage10_8
>         Attachments: DummyProc.java, triggerBug.sql, triggerBug.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