Bug #13187 Updated: Concerning jdtounix() function

ID: 13187 User updated by: studiobl@mageos.com Reported By: studiobl@mageos.com Old Status: Closed Status: Open Bug Type: Calendar related Operating System: Linux Redhat 7.1 PHP Version: 4.0.6 New Comment: 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 ? Previous Comments: ------------------------------------------------------------------------ [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 ------------------------------------------------------------------------ [2001-09-07 03:55:34] hholzgra@php.net what timezone are you in ? ------------------------------------------------------------------------ [2001-09-06 19:18:11] studiobl@mageos.com It's not unresolvable but it must be known : in PHP : jdtounix(today); returns a number of seconds sinc an origin (here we call it A) but in MYSQL : UNIX_TIMESTAMP(today at 00:00:00) returns A minus 7200 seconds that's a difference of 2 hours ! in fact when you do jdtounix(today) it more like jdtounix(today at 02:00:00).... ------------------------------------------------------------------------ Edit this bug report at http://bugs.php.net/?id=13187&edit=1