[DERBY-352] Clobs on insert using streams should not instantiate into memory

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.0.2.2, 10.1.2.1, 10.2.1.6
• Fix Version/s: 10.2.1.6
• Component/s: JDBC, Store
• Environment: all
• Bug behavior facts: Performance
• Assignee: Sunitha Kambhampati
• Reporter: Sunitha Kambhampati
• Created: 14/Jun/05 02:53
• Updated: 04/Jun/13 05:01
• Resolved: 18/Oct/05 01:25

Description

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.

Issue Links

• is related to: DERBY-6237 PreparedStatement.execute() fails starting 10.2 when multiple rows are updated and PreparedStatement.setCharacterStream(int, Reader, int) is used