News Feed
Jobs Feed
Sections




News Archive
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

Chauy.com: LAMP - The Most Popular Server System Ever.

Zend Developer Zone: PHP and MySQL By Example - Sample Chapter

DevArticles.com: Singletons in PHP

Smashing Magazine: Replicating MySQL AES Encryption Methods With PHP

Stefan Mischook's Blog: Installing PHP and MySQL on the Mac with MAMP


Community Events









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


example testing functional event object interview podcast tool api framework zendframework2 unittest opinion community composer release language development code introduction

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