[ http://issues.apache.org/jira/browse/DERBY-902?page=comments#action_12366231 ]
Kathey Marsden commented on DERBY-902: -------------------------------------- I have to say. I never understood the way the error message token separators work. This value seems to translate into that awful non ascii character that prints in error messages ala DERBY-285. > Remove use of String(byte[]) and String(byte[], int, int) constructors in > engine leading to non-portable behaviour > ------------------------------------------------------------------------------------------------------------------ > > Key: DERBY-902 > URL: http://issues.apache.org/jira/browse/DERBY-902 > Project: Derby > Type: Bug > Components: Network Server > Reporter: Daniel John Debrunner > Fix For: 10.2.0.0 > Attachments: DERBY-902_021306.stat, DERBY-902_021306_2.diff > > 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.catalog.SystemProcedures > I generated this list using the Java search in eclipse for references to the > constructors > String(byte[]) > String(byte[],int,int) - no occurrrences in java/engine -- 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
