Re: how to get data out from Clob?

[Kristian Waagan <Kr...@Sun.COM>]

Mikael Sundberg wrote:
> Thanks for the info 
> Does the same problem exist for Blob?
> Will update my testservers and try it.

Hi Mikael,

Did you get around to update your test servers?
If so, did you see a performance improvement you use cases?


Regards,
-- 
Kristian

> 
> -----Original Message-----
> From: Kristian.Waagan@Sun.COM [mailto:Kristian.Waagan@Sun.COM] 
> Sent: den 25 november 2008 14:01
> To: Derby Discussion
> Subject: Re: how to get data out from Clob?
> 
> Mikael Sundberg wrote:
>> Hi
>> Im using derby 10.4.2 and the clientdriver.
>> I changed from 
>>                 BufferedReader r = new BufferedReader(new
>> InputStreamReader(res.getAsciiStream("data")));
>>                 for (String line = r.readLine(); line != null; line =
>> r.readLine())
>>                 {
>>                     w.println(line);
>>                 }
>>
>> To
>> 	String data = res.getString("data");
>>
>> In a recent update to our application since the getString seemed to be
>> twice as fast then. Not entirely sure what versions of derby I tested
> on
>> then.
>> So bacisly I should change back now?
> 
> On the client driver, it doesn't matter (with respect to the bug I'm 
> talking about). I'm afraid you're stuck with the performance problem 
> until you upgrade to a newer version.
> 
>> We don't want to use any unstable
>> version on production so guess I will have to solve it some other way.
> 
>> Il atleast try out the latest version on my testservers to see if that
>> realy is the problem.
>>   
> 
> I would consider using the newest bits from the 10.4 branch. The changes
> 
> after the latest release are bug fixes, not new features.
> You can download test binaries from here 
> http://dbtg.thresher.com/derby/bits/
> Note that these are bits used for the nightly testing and should *not* 
> be used in production without verification and testing.
> 
> Note that the performance problem in this case is severe; the larger the
> 
> Clob the worse the impact (we're talking hours instead of 
> seconds/minutes). I would strongly suggest you test with a newer, though
> 
> unreleased, version.
> 
>