[DERBY-903] Remove use of String(byte[]) and String(byte[], int, int) constructors in testing leading to non-portable behaviour

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.1.3.1
• Fix Version/s: 10.1.3.1
• Component/s: Test
• Assignee: Myrna van Lunteren
• Reporter: Daniel John Debrunner
• Created: 01/Feb/06 06:03
• Updated: 13/Dec/07 09:04
• Resolved: 28/Apr/06 02:19

Description

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.derbyTesting.functionTests.tests.jdbcapi.blobclob4BLOB
org.apache.derbyTesting.functionTests.tests.jdbcapi.resultset
org.apache.derbyTesting.functionTests.tests.lang.coalesceTests
org.apache.derbyTesting.functionTests.tests.store.streamingColumn

I generated this list using the Java search in eclipse for references to the constructors
String(byte[])
String(byte[],int,int) (no occurrences in java/testing)

Issue Links

• relates to: DERBY-575 test blobclob4BLOB fails on OS 390
• relates to: DERBY-658 test harness improvements required for running on non-ASCII systems