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 Tue, 15 Mar 2011 18:36:29 GMT

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

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

Thanks, Mamta. This sounds like good progress. I don't understand the performance implications
of compiling the trigger action every time a firing statement is compiled. I suspect that
the actions are pre-compiled because someone believed that would yield a performance boost.
At a high level, I like the idea of compiling the trigger action along with the firing statement,
if only because it gets us out of the business of asking people to drop and recreate their
triggers when we correct problems like this. Ever since my stint at Sybase, I have not been
a big fan of stored prepared statements--I believe they are a runtime optimization with a
thousand brittle consequences.

At a minimum we would want to make sure that this approach does not break recompilations of
prepared statements which may happen because of table changes. For instance, I am thinking
about what happens when someone alters the table which is the target of the trigger action.

Thanks,
-Rick

> 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, 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