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-2712) If large clob is updated after Reader. the reader continues to point to old data
Date Wed, 13 Jun 2007 10:55:25 GMT

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

Anurag Shekhar updated DERBY-2712:
----------------------------------

    Attachment: derby-2712v3.diff

changes in this patch
1.Checking for SanityManager.DEBUG before calling SanityManager.assert
2.Moved InternalClob.getByteLength in separate call in ClobStreamControl.copyClobContent(InternalClob
clob) to avoid 2806


> If large clob is updated after Reader. the reader continues to point to old data
> --------------------------------------------------------------------------------
>
>                 Key: DERBY-2712
>                 URL: https://issues.apache.org/jira/browse/DERBY-2712
>             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-2712.diff, derby-2712v2.diff, derby-2712v3.diff
>
>
> If a Reader is fetched from a large clob (obtained from ResultSet) a reader linked to
the dvd stream is returned once a set method is called on it the clob data is materialized
in control class but the Reader returned previously continues to point to 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