I have a question sideways in connection to this bug - I did the search for the String(byte[]) constructor in eclipse, and found that in addition to the 4 tests as reported, this is used in the following classes:
- java/engine/org.apache.derby.catalog.SystemProcedures
method SQLCAMESSAGE
- java/drda/org.apache.derby.impl.drda.DRDAConnThread
method readAndSetParams, writeSQLDIAGCI and static assignments for
SQLERRMC_MESSAGE_DELIMETER and SQLERRMC_TOKEN_DELIMITER
Wouldn't the usage there also cause trouble when derby is used in non-fixed encodings?
Myrna
On 1/31/06, Daniel John Debrunner (JIRA) <[email protected]> wrote:
Remove use of String(byte[]) and String(byte[], int, int) constructors in testing leading to non-portable behaviour
-------------------------------------------------------------------------------------------------------------------
Key: DERBY-903
URL: http://issues.apache.org/jira/browse/DERBY-903
Project: Derby
Type: Bug
Components: Test
Versions: 10.2.0.0
Reporter: Daniel John Debrunner
Fix For: 10.2.0.0
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)
--
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
