db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sunitha Kambhampati (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-900) Remove use of String(byte[]) and String(byte[], int, int) constructors in network client leading to non-portable behaviour
Date Mon, 15 May 2006 20:44:07 GMT
    [ http://issues.apache.org/jira/browse/DERBY-900?page=comments#action_12402417 ] 

Sunitha Kambhampati commented on DERBY-900:

Thanks Kathey for committing the p2 cleanup patch on trunk..

Also adding notes here about the testSecMec failure that Kathey mentioned in the previous
comment.  It seems like that was related to her machine environment and probably a manifestation
of same issue mentioned in DERBY-1114.  Kathey mentioned that the test  failed without the
patch on different jvms too.   

I would like the derby900.p2_encodingChange.diff.txt to be ported to 10.1. It is a clean merge.
 The merge command is

svn merge -r 398943:398944 https://svn.apache.org/repos/asf/db/derby/code/trunk/

I merged and then ran derbynetclientmats on ibm142/linux ok. 

Can someone please commit this.  Thanks. 

> Remove use of String(byte[]) and String(byte[], int, int) constructors in network client
leading to non-portable behaviour
> --------------------------------------------------------------------------------------------------------------------------
>          Key: DERBY-900
>          URL: http://issues.apache.org/jira/browse/DERBY-900
>      Project: Derby
>         Type: Bug

>   Components: Network Client
>     Reporter: Daniel John Debrunner
>     Assignee: Sunitha Kambhampati
>      Fix For:
>  Attachments: Derby900.p2.diff.txt, TestEnc.java, derby900.diff.p1.txt, derby900.p2.stat.txt,
derby900.p2_encodingChange.diff.txt, derby900.stat.p1.txt, derby900.test.diff.txt, derby900.test.stat.txt,
derby900_p2_cleanup.diff.txt, derby900_p2_cleanup.stat.txt, for_10.1_derby900.diff.p1.txt,
for_10.1_derby900.stat.p1.txt, testsecmec.zip
> These constructors use the Java default platform encoding to convert the bytes to a String,
this typically leads to bugs on platforms with different encodings.
> Replace with code using fixed conversion, or alternative mechanisms. 
> If the call is required its use should be commented as to why it is required.
> org.apache.derby.client.am.ClobOutputStream - some existing bug?
> org.apache.derby.client.am.DateTime - see DERBY-877
> org.apache.derby.client.am.sqlca
> I generated this list using the Java search in eclipse for references to the constructors
> String(byte[])
> String(byte[],int,int)

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message