db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myrna van Lunteren (JIRA)" <derby-...@db.apache.org>
Subject [jira] Updated: (DERBY-1264) importExportThruIJ.sql supportfiles sqlAnywhere* need to be copied in fixed encoding
Date Fri, 28 Apr 2006 08:01:38 GMT
     [ http://issues.apache.org/jira/browse/DERBY-1264?page=all ]

Myrna van Lunteren updated DERBY-1264:

    Attachment: DERBY-1264_102_20060428.stat

With this patch, the test tools/importExportThruIJ.sql passes on ibm15 on zOS, and with jdk14
on windows.

It fails with ibm14 on zOS, ij making mistakes about the columnnames in the error messages.
I will analyze that and log a separate issue.

I will also look at the behavior on 10.1.2.(4) and see if a backport of this patch to 10.1
is needed (I assume so). 

> 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:
>  Environment: zOS/ OS/390
>     Reporter: Myrna van Lunteren
>     Assignee: Myrna van Lunteren
>     Priority: Trivial
>  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:
For more information on JIRA, see:

View raw message