Displaying 1 result from an estimated 1 matches for "y2k38".
Did you mean:
y2038
2006 May 09
9
Working around the year 2038 bug in Ruby''s Time class?
I would have never imagined that I''d be bitten by the Y2038 bug
someday... but it just happened and, trust me, it hurts!
I have to deal with a database containing datetime fields with dates
up to 2050 and more. ActiveRecord raises an exception because Ruby''s
Time class implementation.
Besides running Ruby on a 64-bit platform, what can be done to avoid that?
Does a