|
Problem IT37123
|
Status: Closed |
JDBC: GETTIMESTAMP() THROWING EXCEPTION AND ALSO RETURNING INCORRECT RESULTS
|
| product: |
IBM CSDK / 5724C2381 / 450 - CSDK 4.50 |
| Problem description: |
When using getTimestamp() to return a datetime year to minute
type, Informix JDBC will throw one of the following exceptions
for an empty string depending on whether using 4.10.JC14 or
4.50.JC5:
4.10.JC14: java.sql.SQLException: System or internal error
java.lang.IllegalArgumentException:
4.50.JC5: java.sql.SQLException: System or internal error
When returning a valid datetime year to minute of "0002-12-31
00:00:00.0", it will instead return the following:
4.10.JC14: 2000-12-31 00:00:00.0
4.50.JC5: 2000-12-31 00:00:00.0
Using Informix JDBC 3.70.JC8, the following is returned for both
tests above (empty string and valid datetime year to minute:
0002-12-31 00:00:00.0 |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* Users of Informix JDBC prior to 4.50.JC7. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Informix JDBC 4.50.JC7. *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* Users of Informix JDBC prior to 4.50.JC7. *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* Upgrade to Informix JDBC 4.50.JC7. *
**************************************************************** |
| Comment |
Fixed in Informix JDBC 4.50.JC7. |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 03.06.2021
02.11.2021
02.11.2021 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
