db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-683) Use correct encoding for ClobOutputStream on client
Date Fri, 17 Feb 2006 16:40:26 GMT
     [ http://issues.apache.org/jira/browse/DERBY-683?page=all ]

Myrna van Lunteren updated DERBY-683:
-------------------------------------

    Attachment: DERBY-683_tstpatch3_2006_02_16.stat
                DERBY-683_tstpatch3_2006_02_16.diff

Attaching an updated patch for the test harness. (DERBY-683_tstpatch03_2006_02_16.*)
This is close to what was created before. 
Compared to deepa's original, it 
- skips any test run with derbyTesting.encoding if the jvm is not jdk15
- does not set file.encoding in the RunSuite & thus will get set & unset for every
test where it applies
- includes a brief mention of the property in the java/testing/READEM.htm

I also took advantage of touching up the README.htm to mention with the remote server functionality
that 
derby.jar needs to be available (although not in the classpath), and to list the junit tests
as a valid test type.


> 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: DERBY-683_tstpatch3_2006_02_16.diff, DERBY-683_tstpatch3_2006_02_16.stat,
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


Mime
View raw message