You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Kathey Marsden (JIRA)" <ji...@apache.org> on 2008/10/07 20:02:46 UTC

[jira] Updated: (DERBY-3883) LOBStreamControl.replaceBytes() leaves temporary files open

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

Kathey Marsden updated DERBY-3883:
----------------------------------

    Fix Version/s: 10.3.3.1

> LOBStreamControl.replaceBytes() leaves temporary files open
> -----------------------------------------------------------
>
>                 Key: DERBY-3883
>                 URL: https://issues.apache.org/jira/browse/DERBY-3883
>             Project: Derby
>          Issue Type: Bug
>          Components: JDBC
>    Affects Versions: 10.4.2.0, 10.5.0.0
>            Reporter: Knut Anders Hatlen
>            Assignee: Knut Anders Hatlen
>            Priority: Minor
>             Fix For: 10.3.3.1, 10.4.2.1, 10.5.0.0
>
>         Attachments: d3883.diff, Derby3883.java
>
>
> I haven't seen any problems as a result of this, but the code that closes and deletes the old temporary file in LOBStreamControl.replaceBytes() looks wrong to me.
> When replaceBytes() is called on a lob that has been materialized into a temporary file, it will create a new file and copy the relevant parts from the old file. But the old file is only closed and deleted if the block that is replaced ends before the last byte of the lob. I believe that the old file should be closed and deleted also when we replace a block that ends at or after the last byte of the original lob.

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