Re: Why is ODBC so difficult?
Dale E. Reed Jr. ( (no email) )
Sun, 01 Mar 1998 12:59:12 -0800
Jeff Woods wrote:
> Many systems store dates in the format "seconds since January 1, 1970,
> 12:00:00 midnight". They store this in a long integer, able to store a
> number of approximately 2.1 billion. There are 28.536 million seconds in
> a year. Thus, there are roughly 2.1 billion seconds between January 1,
> 1970 and some date in the middle of the year 2039.
> (IMO, the designer of this system was stupid, and I'm not referring to
> Dale, I'm referring to the inventor of "seconds since" format -- it's an
> unneeded calculation to figure out leap years, seconds per day, hour, etc,
> and should have been unsigned, to extend it slightly into 2100 in ANY case,
> but that's what format the underlying code of Emerald or SQL uses, and
> that's what Dale had to use... There's be another round of "are you year
> 2039 compliant" issues by then, I'm sure.)
RadiusNT 2.5 uses a different method for resolving expirations
and is not prone to this problem. I just verified a date of
1/1/2199 works fine.
-- Dale E. Reed Jr. (email@example.com)_________________________________________________________________ IEA Software, Inc. | RadiusNT, Emerald, and NT FAQs Internet Solutions for Today | http://www.iea-software.com