[jira] Commented: (DERBY-1615) Rewrite the Clob implementation in the client driver

["Kathey Marsden (JIRA)" <ji...@apache.org>]

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

Kathey Marsden commented on DERBY-1615:
---------------------------------------

I know there has been a lot of work on lobs.  Is this complete? All linked issues, except for DERBY-1599 have been closed.  I think DERBY-1599 is a bug that can just stand on its own.


> Rewrite the Clob implementation in the client driver
> ----------------------------------------------------
>
>                 Key: DERBY-1615
>                 URL: https://issues.apache.org/jira/browse/DERBY-1615
>             Project: Derby
>          Issue Type: Improvement
>          Components: JDBC, Network Client
>            Reporter: Kristian Waagan
>
> The implementation of java.sql.Clob in the client driver is cracking up, and should be rewritten.
> A number of bugs have been discovered, and the implementation has traces of old and/or deprecated features. Further, several mandatory methods (JDBC 3 & 4) have not yet been implemented and could benefit from a fresh start.
> I think maintainability for this piece of code has dropped to an unacceptable level.
> It seems the implementation is based on an assumption that no longer holds; that a Clob object used for input to the database is never passed to the user. The consequence of this, is that the internal state of the Clob object is not valid [at all times], which causes exceptions when the user invokes methods on it.
> A number of related Jira issues have been linked to this issue to aid the reimplementation process.

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