[
https://issues.apache.org/jira/browse/DERBY-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dag H. Wanvik updated DERBY-352:
--------------------------------
Derby Categories: [Performance]
> Clobs on insert using streams should not instantiate into memory
> -----------------------------------------------------------------
>
> Key: DERBY-352
> URL: https://issues.apache.org/jira/browse/DERBY-352
> Project: Derby
> Issue Type: Bug
> Components: JDBC, Store
> Affects Versions: 10.0.2.2, 10.1.2.1, 10.2.1.6
> Environment: all
> Reporter: Sunitha Kambhampati
> Assignee: Sunitha Kambhampati
> Fix For: 10.2.1.6
>
> 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.
-
You can reply to this email to add a comment to the issue online.
