db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kathey Marsden (JIRA)" <j...@apache.org>
Subject [jira] Closed: (DERBY-1615) Rewrite the Clob implementation in the client driver
Date Fri, 08 May 2009 12:47:45 GMT

     [ https://issues.apache.org/jira/browse/DERBY-1615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Kathey Marsden closed DERBY-1615.

       Resolution: Later
    Fix Version/s:

Thanks Kristian, that sounds good to me.  Closing this issue as 'Later. I think I would prefer
to close out these relatively vague major line items and open up incremental improvement suggestions
as they come up or only reopen them if someone wants to actively work on them.  I'd forgotten
about Later as an option.  
BTW, even after the cleanup yesterday, we still have 1074 open issues.  I think on my next
pass (in a few months) I will make more aggressive use of 'Later', so we can trim it to a
more manageable list.

> 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
>             Fix For:
> The implementation of java.sql.Clob in the client driver is cracking up, and should be
> 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

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

View raw message