Nope, it won't. Because by that time we'll be dealing with stardates...
like in startrek.. hehe. For instance right now it's star date 85160.34
City Of St. John's, NL
P.O. Box 908
St. John's, NL
Success is going from failure to failure without a loss of enthusiasm. -
Sir Winston Churchill
Freedom is the right of all sentient beings. - Optimus Prime
Mike Cunningham <mcunning@xxxxxxx>
Sent by: java400-l-bounces@xxxxxxxxxxxx
2008/02/28 12:37 PM
Please respond to
Java Programming on and around the iSeries / AS400
"'Java Programming on and around the iSeries / AS400'"
RE: jt400 timestamp issue
Why would the year 9999 be an invalid year? It will occur eventually
[mailto:java400-l-bounces@xxxxxxxxxxxx] On Behalf Of David Gibbs
Sent: Thursday, February 28, 2008 10:03 AM
To: Java Programming on and around the iSeries / AS400
Subject: Re: jt400 timestamp issue
Mike Cunningham wrote:
We have a DB2/400 database table with a timestamp field that has the
value of 12/31/9999. DB2 is happy with that. I have a PC based java
application using the jt400 jdbc driver to read that file and the
result set appears to return a null value for that date. If the date
is changed to 12/31/2008 it is returned correctly, put back to
12/31/9999 and it's null. Could the jt400 driver be doing this?
Practically speaking, that's an invalid date ... so Java can't deal with
it. The java.sql.Date class is an extension of the java.util.Date class
... which tries to represent a real date. I suspect that jt400 is
seeing a date it can't parse and translating it into null.
I would say that the fact that DB2/400 accepts it is the real bug.
Although I doubt you can get it fixed.
IBM System i - For when you can't afford to be out of business
This is the Java Programming on and around the iSeries / AS400 (JAVA400-L)
To post a message email: JAVA400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
or email: JAVA400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives