[
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
'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: 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.
