You are viewing a plain text version of this content. The canonical link for it is here.
Posted to derby-dev@db.apache.org by "Andrew McIntyre (JIRA)" <de...@db.apache.org> on 2006/05/02 21:53:47 UTC

[jira] Resolved: (DERBY-1264) importExportThruIJ.sql supportfiles sqlAnywhere* need to be copied in fixed encoding

     [ http://issues.apache.org/jira/browse/DERBY-1264?page=all ]
     
Andrew McIntyre resolved DERBY-1264:
------------------------------------

    Fix Version: 10.2.0.0
                 10.1.3.0
                 10.1.2.4
     Resolution: Fixed
     Derby Info:   (was: [Patch Available])

Committed to 10.1 with revision 399023.

> importExportThruIJ.sql supportfiles sqlAnywhere* need to be copied in fixed encoding
> ------------------------------------------------------------------------------------
>
>          Key: DERBY-1264
>          URL: http://issues.apache.org/jira/browse/DERBY-1264
>      Project: Derby
>         Type: Test

>   Components: Test
>     Versions: 10.2.0.0
>  Environment: zOS/ OS/390
>     Reporter: Myrna van Lunteren
>     Assignee: Myrna van Lunteren
>     Priority: Trivial
>      Fix For: 10.2.0.0, 10.1.3.0, 10.1.2.4
>  Attachments: DERBY-1264_102_20060428.diff, DERBY-1264_102_20060428.stat
>
> The test tools/importExportThruIJ.sql fails after the changes for DERBY-658, because the harness now tries to copy the supportfiles testData/importExport/sqlAnywhere1.txt and sqlAnywhere2.txt into local encoding.. This gives the following error:
> Exception in thread "main" sun.io.MalformedInputException
>         at sun.io.ByteToCharUTF8.convert(ByteToCharUTF8.java:278)
> Note: before, DERBY-658, these 2 files would have to be *not* run through native2ascii. The test explicitly assumes the contents to be ASCII (that is, the import indicates "ASCII").  My notes indicate that with 10.1.1, this test then passed with ibm14.
> Because the copying is done based on extension, these two files need to be renamed.

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