db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (DERBY-2349) Accessing a BLOB column twice in an INSERT trigger leads to errors in the value on-disk
Date Thu, 11 Feb 2010 12:06:28 GMT

     [ https://issues.apache.org/jira/browse/DERBY-2349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kristian Waagan resolved DERBY-2349.
------------------------------------

       Resolution: Fixed
    Fix Version/s: 10.6.0.0

Fixed by the combination of DERBY-4477 and DERBY-4520.
Verified against trunk revision 980933, but it would be nice if the reporter verified the
fix as well.

I do not plan to back-port the fix(es) due to the rather signficant changes involved, but
it may be technically possible.

> Accessing a BLOB column twice in an INSERT trigger leads to errors in the value on-disk
> ---------------------------------------------------------------------------------------
>
>                 Key: DERBY-2349
>                 URL: https://issues.apache.org/jira/browse/DERBY-2349
>             Project: Derby
>          Issue Type: Bug
>          Components: SQL
>    Affects Versions: 10.3.1.4
>            Reporter: Daniel John Debrunner
>             Fix For: 10.6.0.0
>
>         Attachments: DERBY_2349_Repro.java
>
>
> Either the BLOB is stored with the incorrect value or the value on disk does not match
the stored length on disk and an exception is raised. The BLOB was supplied as a stream value.
> See this with the new TriggersTest. The text fixture will have a comment with this bug
number showing how to reproduce the problem.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message