db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Anurag Shekhar (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-2711) If large blob is updated after InputStream is fetched (using getBinaryStream), the stream continues to point ot old data
Date Fri, 08 Jun 2007 09:55:26 GMT

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

Anurag Shekhar updated DERBY-2711:
----------------------------------

    Attachment: derby-2711v2.diff

In this patch I have addressed points a b and c of Kristian.

a. Resolved conflicts.
b. Removed Excess docs and added link to java.io.InputStream
c. Replaced tab by spaces.

> If large blob is updated after InputStream is fetched (using getBinaryStream), the stream
continues to point ot old data
> ------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-2711
>                 URL: https://issues.apache.org/jira/browse/DERBY-2711
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC
>    Affects Versions: 10.3.0.0
>            Reporter: Anurag Shekhar
>            Assignee: Anurag Shekhar
>             Fix For: 10.3.0.0
>
>         Attachments: derby-2711.diff, derby-2711v2.diff
>
>
> While using a large blob (so that blob doesn't gets materialized while fetching from
database) getBinaryStream returns stream linked to dvd. After blob is is updated internally
the blob data is materialized in LOBStreamControl class but the stream continues to point
to dvd hence giving out old data.

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