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-3793) Remove unnecessary methods from InternalClob interface
Date Tue, 22 Jul 2008 11:52:31 GMT

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

Kristian Waagan updated DERBY-3793:

    Attachment: derby-3793-1a-remove_getBytePosition.stat

'derby-3793-1a-remove_getBytePosition.diff' removes the getBytePosition method from the interface.
In TemporaryClob it is made private, in StoreStreamClob it is deleted.
I had to delete some package private tests. The implementation of TemporaryClob.getBytePosition
now has to be tested indirectly through InteralClob.insertString, for which there already
are some tests.

> Remove unnecessary methods from InternalClob interface
> ------------------------------------------------------
>                 Key: DERBY-3793
>                 URL: https://issues.apache.org/jira/browse/DERBY-3793
>             Project: Derby
>          Issue Type: Improvement
>          Components: JDBC
>    Affects Versions:
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>            Priority: Trivial
>             Fix For:,
>         Attachments: derby-3793-1a-remove_getBytePosition.diff, derby-3793-1a-remove_getBytePosition.stat
> The method InternalClob.getBytePosition is only used in one internal Clob implementation,
and can be removed to reduce complexity and code volume.
> The method InternalClob.getByteLength can be removed.

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

View raw message