db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mamta A. Satoor (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-5121) Data corruption when executing an UPDATE trigger
Date Tue, 22 Mar 2011 20:48:05 GMT

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

Mamta A. Satoor commented on DERBY-5121:
----------------------------------------

As a bigger solution to having to ask the users to drop and recreate the triggers during upgrade,
it will be ideal if we could internally do this ourselves. I think there are 2 possibilites
1)mark the SPS associated with trigger actions as invalid at the time of upgrade. This way,
when they get used next time, we will recreate the correction trigger action sql
2)drop and recreate the trigger action SPSs at the time of upgrade. I am not sure though if
this will run into privileges/roles issues since the user doing the upgrade may not have permissions
to touch the system tables.

I would like to investigate option 1) and see if it is doable. I will hold on to posting my
patch of remapping and will concentrate on option 1) because if the option 1) works than we
can avoid having to ask the users to drop and recreate the triggers. Thanks

> 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

Mime
View raw message