Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Thu, 10 May 2012 18:58:48 +0000 (UTC)
From: "Kim Haase (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: 
 <972034984.50804.1336676328631.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <254534088.7084.1334863600454.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (DERBY-5698) Document performance issue with 2-arg
 versions of setXXXStream methods for LOBs
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Kim Haase updated DERBY-5698:
-----------------------------

    Attachment: DERBY-5698.zip
                DERBY-5698.stat
                DERBY-5698.diff

Attaching DERBY-5698.diff, DERBY-5698.stat, and DERBY-5698.zip, with changes to the following:

M       src/ref/rrefjavsqlprst.dita
M       src/ref/rrefjdbc4_0summary.dita

I added the following sentence to each topic:

"Omitting the length argument when the stream object is a LOB can impair performance, especially if the method is called repeatedly in an application or if the LOB is a large one."

Please let me know if any change is needed to this information. 
                
> Document performance issue with 2-arg versions of setXXXStream methods for LOBs
> -------------------------------------------------------------------------------
>
>                 Key: DERBY-5698
>                 URL: https://issues.apache.org/jira/browse/DERBY-5698
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation
>    Affects Versions: 10.8.2.2
>            Reporter: Kim Haase
>            Assignee: Kim Haase
>         Attachments: DERBY-5698.diff, DERBY-5698.stat, DERBY-5698.zip
>
>
> The PreparedStatement.setAsciiStream and other methods have a 3-arg form that includes the length of the stream and a 2-arg form that does not. If the 2-arg form is used, Derby has to calculate the length every time the method is called. With LOBs, especially large ones, this can cause a major performance impact, especially if the method is called repeatedly. This should be documented where appropriate.
> Kristian, please feel free to correct or amplify anything I've said here.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira