[ http://issues.apache.org/jira/browse/DERBY-683?page=comments#action_12366662 ]
Andrew McIntyre commented on DERBY-683: --------------------------------------- Hi Myrna, I can't get this patch (derby-683_021006.diff) to apply cleanly due to changes in RunTest. Could you merge your changes and post an updated patch? > Use correct encoding for ClobOutputStream on client > --------------------------------------------------- > > Key: DERBY-683 > URL: http://issues.apache.org/jira/browse/DERBY-683 > Project: Derby > Type: Bug > Components: Network Client > Versions: 10.1.1.1, 10.1.1.0 > Environment: all > Reporter: Sunitha Kambhampati > Assignee: Deepa Remesh > Fix For: 10.2.0.0 > Attachments: ascii.txt, clob.java, derby-683.diff, derby-683_021006.diff, > derby-683_021006.stat, derby-683_tests.diff, derby-683_tests.status > > 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 -- 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
