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 "Kristian Waagan (JIRA)" <ji...@apache.org> on 2008/07/22 14:00:31 UTC

[jira] Commented: (DERBY-3793) Remove unnecessary methods from InternalClob interface

    [ https://issues.apache.org/jira/browse/DERBY-3793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12615595#action_12615595 ] 

Kristian Waagan commented on DERBY-3793:
----------------------------------------

Committed 'derby-3793-1a-remove_getBytePosition.diff' to trunk with revision 678724.
Will backport later with the second patch for this issue.

> 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: 10.5.0.0
>            Reporter: Kristian Waagan
>            Assignee: Kristian Waagan
>            Priority: Trivial
>             Fix For: 10.4.1.4, 10.5.0.0
>
>         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.