[
https://issues.apache.org/jira/browse/DERBY-1264?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dag H. Wanvik updated DERBY-1264:
---------------------------------
Issue Type: Bug (was: Test)
> importExportThruIJ.sql supportfiles sqlAnywhere* need to be copied in fixed
> encoding
> ------------------------------------------------------------------------------------
>
> Key: DERBY-1264
> URL: https://issues.apache.org/jira/browse/DERBY-1264
> Project: Derby
> Issue Type: Bug
> Components: Test
> Affects Versions: 10.2.1.6
> Environment: zOS/ OS/390
> Reporter: Myrna van Lunteren
> Assignee: Myrna van Lunteren
> Priority: Trivial
> Fix For: 10.1.3.1, 10.2.1.6
>
> 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.
-
You can reply to this email to add a comment to the issue online.
