This one time, at band camp, Steve Stearns said:
SS>I actually managed to run into the Y2K38 bug recently. I was using
SS>Castor with Postgresql and kept getting a mysterious complaint about
SS>string index being out of bounds. Something kept getting a 23 character
SS>string instead of the expected 22 character and I wasn't sure what was
SS>causing it. Finally through a little trial and error I realized it was
SS>my date field that was complaining.
SS>
SS>I had my system creating accounts with expiration dates set 100 years in
SS>the future, and of course this is a little beyond 2038 :). I'm not sure
SS>if this is a bug in castor or the underlying implementation of
SS>postgrsql's JDBC driver, but figured I'd mention it here and see if
SS>anybody else had run into it.
Steve,
Could you please post the mapping for this particular field? I'd like to know
how you had it mapped.
Bruce
--
perl -e 'print unpack("u30","<0G)U8V4\@4VYY9&5R\"F9E<G)E=\$\!F<FEI+F-O;0\`\`");'
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
