[ http://issues.apache.org/jira/browse/DERBY-609?page=all ]
Tomohito Nakayama updated DERBY-609:
------------------------------------
Attachment: DERBY-609.patch
I submit patch for DERBY-609 .
Description :
* Modification to client
Now ResultSet returrn InputStream as CloseFilterInputStream filtering
original InputStream.
CloseFilterInputStream serve functionality to be closed , even if close
method of filtered InputStream have no effect .
ResultSet close CloseFilterInputStream when getXXXX method was called .
* Modification to test
Include jdbc/resultsetStream.java in DerbyNetClient suite .
Test :
executed derbyall and found no error .
> Returning ByteArrayInputStream from ResultSet is not appropriate
> ----------------------------------------------------------------
>
> Key: DERBY-609
> URL: http://issues.apache.org/jira/browse/DERBY-609
> Project: Derby
> Type: Bug
> Components: Network Client
> Reporter: Tomohito Nakayama
> Assignee: Tomohito Nakayama
> Attachments: DERBY-609.patch
>
> Point where it is not appropriate :
> 1: Compatibility
> The InputStream returned from result set is closed when other getXXXX method
> was called .
> http://java.sun.com/j2se/1.5.0/docs/api/java/sql/ResultSet.html
> However closing ByteArrayInputStream have no effect at all .
> http://java.sun.com/j2se/1.5.0/docs/api/java/io/ByteArrayInputStream.html#close()
> It seems intended that closable InputStream was returned from result set .
> If ByteArrayInputStream was returned from result set , the stream cannot be
> closed,
> and compatibility would be lost .
> 2: Performance of program
> Information inputted from ByteArrayInputStream needs to be expanded to memory
> as byte[] object .
> If large byte[] object was created for each ByteArrayInputStream object ,
> program will run in bad performance .
> // I think problem is when information typed as LOB was retrieved from
> ResultSet .
> // Because such informations typed as LOB tend to be large amount .
--
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
