Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 68470 invoked from network); 2 May 2006 23:22:22 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 2 May 2006 23:22:22 -0000 Received: (qmail 68603 invoked by uid 500); 2 May 2006 23:22:21 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 68573 invoked by uid 500); 2 May 2006 23:22:21 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 68564 invoked by uid 99); 2 May 2006 23:22:21 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 May 2006 16:22:21 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from [209.237.227.198] (HELO brutus.apache.org) (209.237.227.198) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 02 May 2006 16:22:19 -0700 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 5572F71428D for ; Tue, 2 May 2006 23:21:47 +0000 (GMT) Message-ID: <27931715.1146612107345.JavaMail.jira@brutus> Date: Tue, 2 May 2006 23:21:47 +0000 (GMT+00:00) From: "Tomohito Nakayama (JIRA)" To: derby-dev@db.apache.org Subject: [jira] Commented: (DERBY-782) Improvement on org.apache.derby.impl.jdbc.EmbedBlob#length() In-Reply-To: <39071990.1135315471206.JavaMail.jira@ajax.apache.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/DERBY-782?page=comments#action_12377492 ] Tomohito Nakayama commented on DERBY-782: ----------------------------------------- I read modification of DERBY-438 that length of blob is memoried in org.apache.derby.impl.jdbc.EmbedBlob, if once length() method was called and all of blob was read out. My original intention in this task was to use information of lengh in BinaryToRawStream, which was found as invalid. Then my original intention was not achieved. I'm not exactly sure why information of length in BinaryToRawStream is invalid, though it is likely to be invalid. Here, "likely" means that I think keeping information for length of blob in BinaryToRawStream valid may be difficult and fragile. Well .... The information for length of blob in BinaryToRawStream is a little mystery for me, because I do'nt know the history why it is invalid. > 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 > Fix For: 10.2.0.0 > 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 unknown. -- 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