[
https://issues.apache.org/jira/browse/DERBY-2711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Waagan updated DERBY-2711:
-----------------------------------
Attachment: derby-2711-3a-additional.diff
'derby-2711-3a-additional.diff' must be committed on top of v2, and does the
following:
* Made variable blob final.
* Throws exception that was caught and wrapped.
* Added a comment that the stream will update itself and reflect the new
content in all read/skip methods.
* Changed normal comments into JavaDoc for updateIfRequired.
In addition it removes trailing whitespace and cleans up a few JavaDoc things.
> 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-3a-additional.diff, 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.
