[DERBY-2652] Clob.setCharacterStream differs between embedded and client driver

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.2.2.0, 10.3.1.4
• Fix Version/s: 10.3.1.4
• Component/s: JDBC
• Assignee: Unassigned
• Reporter: Kristian Waagan
• Created: 15/May/07 15:13
• Updated: 20/Jun/07 11:37
• Resolved: 20/Jun/07 11:37

Description

Clob.setCharacterStream behaves differently depending on whether you use the embedded or the client driver.
Sample output from the repro:

(embedded) Initial : 123456789
(embedded) After : 12__56789

(client) Initial : 123456789
(client) After : 12__

As can be seen, the client driver truncates the Clob value when it writes to it, whereas the embedded driver does not and instead replaces existing characters with those written to the character stream.

(BTW: I know the title is not perfectly accurate, but it got so long when explaining that it is when you actually write to the stream returned by Clob.setCharacterStream the result differs.)

Issue Links

• is part of: DERBY-310 Document and/or change Derby client code to match behavior with Embedded driver where possible.
• is related to: DERBY-2346 Provide set methods for clob for embedded driver
• is related to: DERBY-572 Add support for Clob.setCharacterStream(), Clob.setAsciiStream()and Blob.setBinaryStream in embedded, it is already supported in client.