[DERBY-683] Use correct encoding for ClobOutputStream on client

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.1.1.0, 10.1.2.1
• Fix Version/s: 10.1.3.1, 10.2.1.6
• Component/s: Network Client
• Environment: all
• Assignee: Deepa
• Reporter: Sunitha Kambhampati
• Created: 05/Nov/05 10:55
• Updated: 12/Jul/06 01:49
• Resolved: 18/May/06 05:34

Description

In client, there is code in ClobOutputStream which uses this api - new String(byte[]). Per the java api http://java.sun.com/j2se/1.4.2/docs/api/java/lang/String.html#String(byte[]) ,this will construct a string by decoding the array of bytes using the platform's default character set.

org.apache.derby.client.am.ClobOutputStream is used for Clob.setAsciiStream and the write methods use the String(byte[]) which is incorrect because it will use the default platform encoding. Per the jdbcapi , this should use ascii encoding.

In areas related to Clobs, also check for other places where String(byte[]) is used,as it may not be the desired behavior.

Dan pointed this problem here : http://issues.apache.org/jira/browse/DERBY-463?page=comments#action_12356742

Issue Links

• is blocked by: DERBY-1027 encodingTests suite cannot be run on JDK 1.4.2
• relates to: DERBY-658 test harness improvements required for running on non-ASCII systems
• relates to: DERBY-1027 encodingTests suite cannot be run on JDK 1.4.2