db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Matrigali <mikem_...@sbcglobal.net>
Subject Re: [jira] Updated: (DERBY-352) Clobs on insert using streams should not instantiate into memory
Date Thu, 06 Oct 2005 18:09:04 GMT
I have reviewed, run successful tests and committed this patch as
svn:   306822
Sunitha Kambhampati (JIRA) wrote:

>      [ http://issues.apache.org/jira/browse/DERBY-352?page=all ]
> 
> Sunitha Kambhampati updated DERBY-352:
> --------------------------------------
> 
>     Attachment: Derby352.diff.txt
> 
> 
>>Clobs on insert  using streams should not instantiate into memory
>>-----------------------------------------------------------------
>>
>>         Key: DERBY-352
>>         URL: http://issues.apache.org/jira/browse/DERBY-352
>>     Project: Derby
>>        Type: Bug
>>  Components: JDBC, Performance, Store
>>    Versions: 10.0.2.1, 10.0.2.0
>> Environment: all
>>    Reporter: Sunitha Kambhampati
>>    Assignee: Sunitha Kambhampati
>> Attachments: Derby352.diff.txt
>>
>>Currently in derby, for an insert on a clob using setCharacterStream what will happen
is , the entire stream will be materialized into a char array and sent to store for the insert.

>>see  - SQLVarChar.normalize, where getString() is called and SQLChar.getString() will
materiliaze the entire stream into a char array ( SQLChar.readExternal). 
>>The store layer must actually drive the streaming. 
> 
> 

Mime
View raw message