iginal Message-
> From: Michael Meltzer [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, July 10, 2001 4:15 PM
> To: Theo Van Dinter; [EMAIL PROTECTED]
> Subject: Re: unix_timestamp doesn't understand year 2038
>
>
> it not a bug, it is a feature, complain to Tomas Riche,
nter
Newport, RI 02841
1-800-669-6892 x28990
-Original Message-
From: Dinkler, Fred [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, July 11, 2001 1:14 PM
To: Michael Meltzer
Cc: Mysql List (E-mail)
Subject: RE: unix_timestamp doesn't understand year 2038
|
||
--
|__|__|
|| ||
ooO Ooo
-Original Message-
From: Michael Meltzer [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 10, 2001 4:15 PM
To: Theo Van Dinter; [EMAIL PROTECTED]
Subject: Re: unix_timestamp doesn't understand year 2038
it
On Tue, Jul 10, 2001 at 04:15:03PM -0400, Michael Meltzer wrote:
> it not a bug, it is a feature, complain to Tomas Riche, 68 years (2038-1970)
> is all the seconds that fit in 2^31 or a signed long number, which is how
> the timestamp was defined a long time ago, it was always figured that some
>
Van Dinter" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, July 10, 2001 3:59 PM
Subject: unix_timestamp doesn't understand year 2038
> >Description:
> unix_timestamp doesn't understand year 2038.
> >How-To-Repeat:
> this works:
> se
>Description:
unix_timestamp doesn't understand year 2038.
>How-To-Repeat:
this works:
select unix_timestamp("2037-12-31 23:59:59");
this doesn't:
select unix_timestamp("2038-01-01 00:00:00");
>Fix:
unknown. e
