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

[ http://issues.apache.org/jira/browse/DERBY-903?page=comments#action_12376636 ] Andrew McIntyre commented on DERBY-903: --- Committed 10.1 patch with revision 397394. > Remove use of String(byte[]) and String(byte[], int, int) constructors in > testing

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

[ http://issues.apache.org/jira/browse/DERBY-903?page=comments#action_12366571 ] Myrna van Lunteren commented on DERBY-903: -- Hi Andrew, Thx for looking at this. I would say, if no one objects, to go ahead with this change at this point, I will ma

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

[ http://issues.apache.org/jira/browse/DERBY-903?page=comments#action_12366565 ] Andrew McIntyre commented on DERBY-903: --- Hi Myrna, I took a look at the latest patch for this, DERBY-903_021306.diff. It looks good, except it's not clear to me that th

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

[ http://issues.apache.org/jira/browse/DERBY-903?page=comments#action_12366185 ] Myrna van Lunteren commented on DERBY-903: -- I ran all 4 tests with jdk15, embedded, DerbyNet and DerbyNetClient. coalesceTests and streamingColumn don't normally run wi