Bug #13187 Updated: Concerning jdtounix() function
| From: | derick@php.net | Date: | Sat, 25 May 2002 10:43:23 +0000 |
| Subject: | Bug #13187 Updated: Concerning jdtounix() function | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-8501@lists.php.net to get a copy of this message | ||
ID: 13187
Updated by: derick@php.net
Reported By: studiobl@mageos.com
-Status: Open
+Status: Closed
Bug Type: Calendar related
Operating System: Linux Redhat 7.1
PHP Version: 4.0.6
New Comment:
Updated documentation for jdtounix > closing.
Previous Comments:
------------------------------------------------------------------------
[2001-09-07 08:02:39] studiobl@mageos.com
I havn't seen the last comment I was editing,
perhaps that's an explanation but it must be noticed
in the function help...
------------------------------------------------------------------------
[2001-09-07 08:00:42] studiobl@mageos.com
By the way I don't know why there would be a link
between my system date and those operations ???
Friday 2001-09-07 -> jd=2462160
jdtounix(2462160)=999820800 sec
UNIX_TIMESTAMP('2001-09-07 00:00:00')=999813600 sec
but : UNIX_TIMESTAMP('2001-09-07 02:00:00')=999820800 sec
Is it clear ?
------------------------------------------------------------------------
[2001-09-07 07:55:44] hholzgra@php.net
so jdtounix returns localtime while
mysql unix_timestamp returns GMT
------------------------------------------------------------------------
[2001-09-07 07:48:19] derick@php.net
France is GMT+2 during summer and GMT+1 during winter
Derick
------------------------------------------------------------------------
[2001-09-07 07:29:13] studiobl@mageos.com
I m in FRANCE(Paris) GMT or GMT+1 I think
------------------------------------------------------------------------
The remainder of the comments for this report are too long. To view
the rest of the comments, please view the bug report online at
http://bugs.php.net/13187
--
Edit this bug report at http://bugs.php.net/?id=13187&edit=1