db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sunitha Kambhampati (JIRA)" <derby-...@db.apache.org>
Subject [jira] Resolved: (DERBY-352) Clobs on insert using streams should not instantiate into memory
Date Mon, 17 Oct 2005 16:27:47 GMT
     [ http://issues.apache.org/jira/browse/DERBY-352?page=all ]
Sunitha Kambhampati resolved DERBY-352:

    Resolution: Fixed

Fix committed in svn:   306822.  

> 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:,,,,
>  Environment: all
>     Reporter: Sunitha Kambhampati
>     Assignee: Sunitha Kambhampati
>      Fix For:
>  Attachments: Derby352.diff.txt, Derby352.stat.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. 

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