You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Sunitha Kambhampati (JIRA)" <de...@db.apache.org> on 2005/10/17 18:27:48 UTC
[jira] Closed: (DERBY-352) Clobs on insert using streams should not instantiate into memory
[ http://issues.apache.org/jira/browse/DERBY-352?page=all ]
Sunitha Kambhampati closed DERBY-352:
-------------------------------------
> 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.2.0.0, 10.1.2.0, 10.1.1.2, 10.1.1.1, 10.0.2.2
> Environment: all
> Reporter: Sunitha Kambhampati
> Assignee: Sunitha Kambhampati
> Fix For: 10.2.0.0
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira