db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tomohito Nakayama (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-782) Improvement on org.apache.derby.impl.jdbc.EmbedBlob#length()
Date Fri, 23 Dec 2005 06:07:31 GMT
    [ http://issues.apache.org/jira/browse/DERBY-782?page=comments#action_12361165 ] 

Tomohito Nakayama commented on DERBY-782:

Current implementation of org.apache.derby.impl.jdbc.EmbedBlob#length() have some problematic
If length() method was called whenBinaryToRawStream was being read, the BinaryToRawStream
was finished. 

Attached testLob4.java shows this behavior. 

naka@rufelza:~/derby/test/20051223$ java testLob4 
Here goes 1st stream 
Here continue 1st stream 

This problematic behavior may be resolved spontaneously in this issue. 

> Improvement on org.apache.derby.impl.jdbc.EmbedBlob#length()
> ------------------------------------------------------------
>          Key: DERBY-782
>          URL: http://issues.apache.org/jira/browse/DERBY-782
>      Project: Derby
>         Type: Bug
>   Components: JDBC
>     Reporter: Tomohito Nakayama
>  Attachments: testLob4.java
> Now, org.apache.derby.impl.jdbc.EmbedBlob#length() method read out whole  BinaryToRawStream
to know exact length.
> On the other hand,  BinaryToRawStream have some commented-out inplementation of having
information for length.
> I think the information of lengh in BinaryToRawStream should be restored to be used in
.org.apache.derby.impl.jdbc.EmbedBlob#length(), because read out whole stream can be expensive
processing when streamed information was large.
> There exists a subject that reliability of lengh information in BinaryToRawStream is

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message