On 11-Jul-01 Dinkler, Fred wrote:
> UNIX version of Y2K problem...
>
No, it is not, RTFM (message).
mysql> select unix_timestamp("2038-01-01 00:00:00");
+---------------------------------------+
| unix_timestamp("2038-01-01 00:00:00") |
+---------------------------------------+
| 0 |
+---------------------------------------+
1 row in set (0.00 sec)
mysql> select FROM_UNIXTIME(0x7fffffff);
+---------------------------+
| FROM_UNIXTIME(0x7fffffff) |
+---------------------------+
| 2038-01-18 19:14:07 |
+---------------------------+
1 row in set (0.01 sec)
mysql> select version();
+-----------+
| version() |
+-----------+
| 3.23.38 |
+-----------+
1 row in set (0.01 sec)
> \\|//
> (@ @)
> -------oOO---(_)---OOo--------
>| |
>| Fred Dinkler |
>| SVP Technology |
>| DFII Atlanta |
>| Office: 01.770.596.1443 |
>| |
> ------------------------------
> |__|__|
> || ||
> 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 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
> would change the base year sooner or later. Or the programmer view ;-) that
> "I will be retired by then so it will be the next person problem", or better
> yet "The software will last that long ha ha ha :-). I subspect someone with
> refine it to a 64 bit number one of these days. But this is not a bug.
>
> MJM
>
>
> ----- Original Message -----
> From: "Theo 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:
>> select unix_timestamp("2037-12-31 23:59:59");
>> this doesn't:
>> select unix_timestamp("2038-01-01 00:00:00");
>> >Fix:
>> unknown. everything through "Jan 19 03:14:07 2038 GMT" should be
>> valid.
>>
>> >Submitter-Id: <submitter ID>
>> >Originator: Theo Van Dinter
>> >Organization:
>> Kluge.Net - WWW Access and Internet Education Network
>> >MySQL support: [none | licence | email support | extended email support ]
>> >Synopsis: unix_timestamp not handling year 2038
>> >Severity: non-critical
>> >Priority: medium
>> >Category: mysql
>> >Class: sw-bug
>> >Release: mysql-3.23.39 (Official MySQL RPM)
>>
>> >Environment:
>>
>> System: Linux eclectic 2.2.19 #1 Mon Apr 9 15:10:02 EDT 2001 i586 unknown
>> Architecture: i586
>>
>> Some paths: /usr/bin/perl /usr/bin/make /usr/bin/gmake /usr/bin/gcc
> /usr/bin/cc
>> GCC: Reading specs from
> /usr/lib/gcc-lib/i386-redhat-linux/egcs-2.91.66/specs
>> gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)
>> Compilation info: CC='egcs'
> CFLAGS='-O6 -fno-omit-frame-pointer -mpentium' CXX='egcs'
>
> CXXFLAGS='-O6 -fno-omit-frame-pointer -felide-constructors -fno-ex
> ceptions -fno-rtti -mpentium' LDFLAGS=''
>> LIBC:
>> lrwxrwxrwx 1 root root 13 Oct 6 2000 /lib/libc.so.6 ->
> libc-2.1.3.so
>> -rwxr-xr-x 1 root root 4101836 Jan 15 10:49 /lib/libc-2.1.3.so
>> -rw-r--r-- 1 root root 20273324 Jan 15 10:49 /usr/lib/libc.a
>> -rw-r--r-- 1 root root 178 Jan 15 10:49 /usr/lib/libc.so
>> lrwxrwxrwx 1 root root 10 Nov 17 2000
> /usr/lib/libc-client.a -> c-client.a
>> Configure command:
> ./configure --disable-shared --with-mysqld-ldflags=-all-static --with-clien
> t-ldflags=-all-static --without-berkeley-db --without-innodb --enable-assemb
> ler --with-mysqld-user=mysql --with-unix-socket-path=/var/lib/mysql/mysql.so
> ck --prefix=/ --with-extra-charsets=complex --exec-prefix=/usr --libexecdir=
> /usr/sbin --sysconfdir=/etc --datadir=/usr/share --localstatedir=/var/lib/my
> sql --infodir=/usr/info --includedir=/usr/include --mandir=/usr/man
> '--with-comment=Official MySQL RPM'
>> Perl: This is perl, version 5.005_03 built for i386-linux
>>
>> ---------------------------------------------------------------------
>> Before posting, please check:
>> http://www.mysql.com/manual.php (the manual)
>> http://lists.mysql.com/ (the list archive)
>>
>> To request this thread, e-mail <[EMAIL PROTECTED]>
>> To unsubscribe, e-mail
> <[EMAIL PROTECTED]>
>> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
>>
>>
>
>
> ---------------------------------------------------------------------
> Before posting, please check:
> http://www.mysql.com/manual.php (the manual)
> http://lists.mysql.com/ (the list archive)
>
> To request this thread, e-mail <[EMAIL PROTECTED]>
> To unsubscribe, e-mail <[EMAIL PROTECTED]>
> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
>
>
> ---------------------------------------------------------------------
> Before posting, please check:
> http://www.mysql.com/manual.php (the manual)
> http://lists.mysql.com/ (the list archive)
>
> To request this thread, e-mail <[EMAIL PROTECTED]>
> To unsubscribe, e-mail <[EMAIL PROTECTED]>
> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
--
Don Read [EMAIL PROTECTED]
-- It's always darkest before the dawn. So if you are going to
steal the neighbor's newspaper, that's the time to do it.
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
