News Feed
Sections




News Archive
Looking for more information on how to do PHP the right way? Check out PHP: The Right Way

Pumka.net:
Why MySQL timestamp is 24 seconds different from PHP
October 26, 2010 @ 11:24:31

On the Pumka.net blog, Anton Oliink has an interesting problem where his timestamp on the PHP side of his application was different than the one on his MySQL backend's side - by 24 seconds, in fact.

You may find that timestamp value returned by MySQL UNIX_TIMESTAMP() function is 24 seconds grater than those returned by PHP functions and classes like strtotime(), mktime, DateTime::getTimestamp(), Zend_Date::getTimestamp().

As it turns out, the issue isn't' really an "issue" after all - it's caused by MySQL's compensation for leap seconds. He gives a few ways you can avoid it being an issue in your application, though: disable leap seconds, only convert to timestamps on the PHP side or just use the "unix_timestamp()" and "from_unixtime()" methods to work with the values.

1 comment voice your opinion now!
mysql timestamp second leapsecond


blog comments powered by Disqus

Similar Posts

Zend Developer Zone: Getting Started with Drizzle and PHP

Code2Learn.com: Using HighCharts with php , MySQL and CodeIgniter

PHPBuilder.com: Use jQuery to Build a Newsletter Subscription Popup with a MySQL/PHP Backend

DeveloperTutorials.com: Scraping Links With PHP

CodeForest.net: Key/value tables and how to use them in PHP and MySQL


Community Events

Don't see your event here?
Let us know!


install example framework introduction php7 api symfony2 community version laravel conference performance voicesoftheelephpant extension opinion series interview podcast release library

All content copyright, 2015 PHPDeveloper.org :: info@phpdeveloper.org - Powered by the Solar PHP Framework