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] Updated: (DERBY-2349) Accessing a BLOB column twice in an INSERT trigger leads to errors in the value on-disk
Date Mon, 06 Jul 2009 20:15:14 GMT

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

Rick Hillegas updated DERBY-2349:
---------------------------------

      Issue & fix info: [Repro attached]
               Urgency: Normal
    Bug behavior facts: [Data corruption]

Triaging for 10.5.2: assigned normal urgency, flagged as data corruption, noted that a repro
is available.

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