[ 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-2b-remove_getByteLength.stat derby-3793-2b-remove_getByteLength.diff 'derby-3793-2b-remove_getByteLength.diff' adds another test, adds/changes documentation for InternalClob.getRawByteStream, removes the InternalClob.getByteLength, and does the required changes for the removal. Regarding the test, I changed it to also add an id to the test table to be able to select specific Clobs. Rerunning suites.All and derbyall, no errors so far. Patch ready for review. > 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.2.0, 10.5.0.0 > > Attachments: derby-3793-1a-remove_getBytePosition.diff, > derby-3793-1a-remove_getBytePosition.stat, > derby-3793-2a-remove_getByteLength.diff, > derby-3793-2a-remove_getByteLength.diff, > derby-3793-2a-remove_getByteLength.stat, > derby-3793-2b-remove_getByteLength.diff, > derby-3793-2b-remove_getByteLength.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.