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

Kathey Marsden updated DERBY-877:
---------------------------------

    Attachment: derby-877.diff

The patch fixes issues with getString, getTimeStamp, getDate and getTime on 
TIMESTAMP, DATE and TIME columns when the client JVM encoding does not match 
the server encoding for the characters being evaluated in DateTime.java methods

- Changes the following methods in DateTime.java to take encoding parameter and 
create string based on encoding.
dateBytesToDate, timeBytesToTime, timeBytesToTimeStamp, dateBytesToTimeStamp, 
timestampBytesToDate, timestampBytesToTime

- Changes calling code to pass column encoding and throw SQLExceptions for 
UnsupportedEncoding  exceptions if thrown from the methods above.

Tests: derbyall  passed as did  the repro attached to this issue on Windows  
with Sun JDK 1.5 (note repro won't run with jdk 1.4.2).
I still do not have a solution for testing within the harness on systems  where 
the JVM encoding  does match the server encoding.
 Any ideas on testing  solutions are welcome. 


> zOS - with DerbyClient getDate(#) fails with IllegalArgumentException - 
> unsupported date format - resultset.java
> ----------------------------------------------------------------------------------------------------------------
>
>          Key: DERBY-877
>          URL: http://issues.apache.org/jira/browse/DERBY-877
>      Project: Derby
>         Type: Bug
>   Components: Network Client
>     Versions: 10.1.1.0
>  Environment: OS/390 with classic (IBM) jvm142
>     Reporter: Myrna van Lunteren
>     Assignee: Kathey Marsden
>  Attachments: TestEnc.java, derby-877.diff
>
> The test lang/resultset.java fails with DerbyNetClient on zOS 
> because ResultSet.getDate(#) fails with an 
> java.lang.IllegalArgumentException - unsupported date format.
> This is the stack trace with 10.2 debug version (but it fails 
> with 10.1 also):
> ------------------
> ....
> getBytes(dt) got exception
> Data Conversion SQLException
> FAIL -- unexpected exception: 
> java.lang.IllegalArgumentException: Unsupported date format!
> java.lang.IllegalArgumentException: Unsupported date format!
>         at 
> org.apache.derby.client.am.DateTime.dateBytesToDate(DateTime.java:63)
>         at 
> org.apache.derby.client.am.Cursor.getDATE(Cursor.java:400)
>         at 
> org.apache.derby.client.am.Cursor.getDate(Cursor.java:712)
>         at 
> org.apache.derby.client.am.ResultSet.getDate(ResultSet.java:687)
>         at 
> org.apache.derbyTesting.functionTests.tests.jdbcapi.resultset.main(Unknown 
> Source)
> ------------------
> Note: does not fail with jcc.
> Also, test lang/updatableResultSet.java failed with e.g.:
>       - instead of 'Got expected exception : Illegal Conversion' :
>                    'Got expected exception : Unsupported date format!' . 
>       - instead of 'Got expected exception : Illegal Conversion' :
>                    'Got expected exception : nanos > 99999999999 or < 0' .

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

Reply via email to