[
https://issues.apache.org/jira/browse/DERBY-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12707286#action_12707286
]
Kristian Waagan commented on DERBY-1615:
----------------------------------------
No, the issue isn't complete. Most of the recent work has been in the core LOB
implementation in the embedded driver. Some work has also been done on the
client implementation.
The question is more whether it will ever be fixed in the near future, or if we
should resolve it as either "Later" or "Won't fix".
Rewriting the Clob implementation in the client driver could very well boost
maintainability in the long term and result in increased performance, but at
the same time it is likely that new bugs will be introduced (despite our test
suite). We may also need some substantial changes in the client/server
communication. To me, it sounds like these changes should go into a new major
version release (i.e. 11.0).
If nobody objects, I'll set the affects version to 11.0, and resolve the issue
as "Later".
> 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.
