Goof morning:
What you are seeing is the side effect of Unix time starting on
January 1, 1970 and being counted, by the second, since then. In 2037
the 32 bit timestamp will roll from 0x7FFFFFFF to 0x80000000. This is
the Unix version of the Y2K problem. It has been solved by going to a
64 bit timestamp.
MySQL is just being 'the canary in the coal mine'.
Thorin
________________________________
From: Rick Cook [mailto:remedyr...@gmail.com]
Sent: Monday, February 16, 2009 11:02 PM
Subject: Re: Date greater than 2037 in remedy
I am guessing that going to a 64 bit operating system will remove that
limitation.
Rick
Sent from my Verizon Wireless BlackBerry
________________________________
From: Aditya C
Date: Tue, 17 Feb 2009 10:14:45 +0530
To: <arslist@ARSLIST.ORG>
Subject: Date greater than 2037 in remedy
**
Hello,
Remedy cannot take date more than year 2037.... anything we can do to
have it more than this.
Regards,
Aditya
__Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are"
html___
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: RMI Solutions ARSlist: "Where the Answers Are"
