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

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 10.1.1.0, 10.1.2.1, 10.1.3.1, 10.2.1.6
• Fix Version/s: 10.1.3.1, 10.2.1.6
• Component/s: Network Client
• Issue & fix info: Patch Available
• Assignee: Unassigned
• Reporter: Daniel John Debrunner
• Created: 01/Feb/06 05:49
• Updated: 20/Mar/07 23:37
• Resolved: 18/May/06 23:38

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.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)