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] Created: (DERBY-2711) If large blob is updated after InputStream is fetched (using getBinaryStream), the stream continues to point ot old data
Date Mon, 28 May 2007 07:50:15 GMT
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
            Reporter: Anurag Shekhar
            Assignee: Anurag Shekhar
             Fix For: 10.3.0.0


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