db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kristian Waagan (JIRA)" <derby-...@db.apache.org>
Subject [jira] Created: (DERBY-1615) Rewrite the Clob implementation in the client driver
Date Mon, 31 Jul 2006 14:00:13 GMT
Rewrite the Clob implementation in the client driver
----------------------------------------------------

                 Key: DERBY-1615
                 URL: http://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.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message