#36338 [Bgs]: Integer Timestamps are not enough!
| From: | derick@php.net | Date: | Fri, 10 Feb 2006 12:12:13 +0000 |
| Subject: | #36338 [Bgs]: Integer Timestamps are not enough! | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-93103@lists.php.net to get a copy of this message | ||
ID: 36338
Updated by: derick@php.net
Reported By: carsten dot moldenhauer at mailbox dot tu-dresden dot
d
Status: Bogus
Bug Type: Date/time related
Operating System: Linux
PHP Version: 5.1.2
New Comment:
Also the new date/time functionality does support 64 bits... except
that it's not enabled yet
Previous Comments:
------------------------------------------------------------------------
[2006-02-09 14:51:25] tony2001@php.net
This is OS limitation and PHP has nothing to do with it.
------------------------------------------------------------------------
[2006-02-09 12:27:36] carsten dot moldenhauer at mailbox dot tu-dresden
dot d
Description:
------------
Hello PHP Team.
I recently discovered a problem with standard timestamps. They are
stored as integers. Integers have a range up to 2147483647.
date( "Y-m-d H:i:s", 2147483647 ) results in:
2038-01-19 04:14:07
If you got a date after 2038 in text format and want to convert it to
integer, you will get back 2147483647. So you are back in 2038 again.
I would dislike to see all the time related PHP applications break on
the above date.
Is there any possibility to switch timestamps to long?
(btw, the same occurs with dates before 1901-12-13 21:45:52 which is
date( "Y-m-d H:i:s, -2147483648 ))
I am looking forward to your answers.
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=36338&edit=1