db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Daniel John Debrunner (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-575) test blobclob4BLOB fails on OS 390
Date Sat, 17 Sep 2005 14:49:54 GMT
    [ http://issues.apache.org/jira/browse/DERBY-575?page=comments#action_12329609 ] 

Daniel John Debrunner commented on DERBY-575:
---------------------------------------------

Or should the test read the file with a fixed encoding so that the size remains as the test
expects.

Not sure though what is doing the conversion to EBCDIC, when you run on OS 390, hopefully
you don't have to covert evryrthing before running the tests.

> test blobclob4BLOB fails on OS 390
> ----------------------------------
>
>          Key: DERBY-575
>          URL: http://issues.apache.org/jira/browse/DERBY-575
>      Project: Derby
>         Type: Bug
>   Components: Test
>     Versions: 10.1.1.0
>  Environment: OS/390 (z/OS 1.06; IBM j2RE 1.4.2)
>     Reporter: Myrna van Lunteren
>     Priority: Minor
>      Fix For: 10.2.0.0

>
> The subtest clobNegativeTest_Derby265 in test jdbcapi/blobclob4BLOB assumes that the
length of the file used (aclob.txt) is 300000 but on OS 390 (z/OS), after conversion to EBCDIC,
the length is 297000. The test should be modified to not use a hardcoded size.

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


Mime
View raw message