[jira] Updated: (DERBY-575) test blobclob4BLOB fails on OS 390

["Myrna van Lunteren (JIRA)" <de...@db.apache.org>]

     [ http://issues.apache.org/jira/browse/DERBY-575?page=all ]

Myrna van Lunteren updated DERBY-575:
-------------------------------------

    Attachment: DERBY-575_102_20060424.stat
                DERBY-575_102_20060424.diff

Attached is a patch for this issue - DERBY-575_102_20060424.*

It contains changes to and for the tests:
jdbcapi/blobclob4BLOB.java
jdbcapi/lobStreams.java
tools/ieptests.sql

The changes boil down to ensuring that appropriate mechanisms are used to accessing supported files - and in the case of blobclob4BLOB and lobStreams, I ended up copying the supportfiles because they were used by other tests with another encoding. So now, the .utf tests are copied unchanged, i.e. in UTF-8 encoding, and the .txt files are copied into local encoding.



> 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
>     Assignee: Myrna van Lunteren
>     Priority: Minor
>      Fix For: 10.2.0.0
>  Attachments: DERBY-575_102_20060424.diff, DERBY-575_102_20060424.stat
>
> 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