db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <j...@apache.org>
Subject [jira] Updated: (DERBY-2646) Cleanup of Clob control/support structures
Date Tue, 29 May 2007 16:00:16 GMT

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

Kristian Waagan updated DERBY-2646:

    Attachment: derby-2646-03a-internalclob.diff

'derby-2646-03a-internalclob.diff' deprecates version 02a.
The patch defines a new interface for internal Clob objects. The point of this is to make
better use of OO programming techniques, and also to split the code into smaller pieces. This
will make it easer to both review and debug.

I plan to have two imlementations:
 a) StoreStreamClob - a read-only Clob working on streams from store
 b) ClobStreamControl - a writable Clob working on a memory or disk image of the content

I plan to rename the latter to TemporaryClob, as Derby operates on copies of the Clob value
when modifications are done.
The switch between the implementations/representations is one-way; you operate on store streams
until you modify the Clob. Note that using Connection.createClob() will create a temporary

As a side note, the matter of representing the temporary Clob in memory or on disk is left
to LOBStreamControl.

This patch will be committed shortly.

More patches will follow.

> Cleanup of Clob control/support structures
> ------------------------------------------
>                 Key: DERBY-2646
>                 URL: https://issues.apache.org/jira/browse/DERBY-2646
>             Project: Derby
>          Issue Type: Sub-task
>          Components: JDBC
>    Affects Versions:
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>         Attachments: derby-2646-01a_trailing_space.diff, derby-2646-01a_trailing_space.stat,
derby-2646-02a-clob-reorg.diff, derby-2646-02a-clob-reorg.stat, derby-2646-03a-internalclob.diff

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

View raw message