I actually managed to run into the Y2K38 bug recently. I was using
Castor with Postgresql and kept getting a mysterious complaint about
string index being out of bounds. Something kept getting a 23 character
string instead of the expected 22 character and I wasn't sure what was
causing it. Finally through a little trial and error I realized it was
my date field that was complaining.
I had my system creating accounts with expiration dates set 100 years in
the future, and of course this is a little beyond 2038 :). I'm not sure
if this is a bug in castor or the underlying implementation of
postgrsql's JDBC driver, but figured I'd mention it here and see if
anybody else had run into it.
---Steve
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
