[ http://issues.apache.org/jira/browse/DERBY-900?page=all ]
Sunitha Kambhampati updated DERBY-900:
--------------------------------------
Attachment: derby900.test.diff.txt
derby900.test.stat.txt
I am attaching a patch 'derby900.test.diff.txt, derby900.test.stat.txt' that
affects only tests.
Changes are
-- remove the ConcurrentImplicitCreateSchema from the encodingTests suite. We
dont run the ConcurrentImplicitCreateSchema test on trunk(10.2) because it has
a high rate of failure on different platforms.
-- add a new test (TestEnc) that repros the derby-583 and the issues that are
fixed as a result of DERBY-900 and DERBY-901 and DERBY-902
I ran the encodingTests suite with jdk15 and tests passed OK.
Can someone please review and commit this patch. 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: 10.2.0.0
> Attachments: TestEnc.java, derby900.diff.p1.txt, derby900.stat.p1.txt,
> derby900.test.diff.txt, derby900.test.stat.txt,
> for_10.1_derby900.diff.p1.txt, for_10.1_derby900.stat.p1.txt
>
> 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:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
