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

WaxJelly Blog: Using PHP to make a MySQL "abstraction layer"

Christian Spanning\'s Blog: PHP development on Mac OS X

HowToForge.com: The Ultimate Media Server - Apache+SSL , PHP, MySQL and Jinzora

Justin Carmony's Blog: MySQL, Redis, and a Billion Rows - A Love Story

Sebastian Begmann's Blog: Partitioning with Dates in MySQL 5.1


Community Events





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


interview framework release package symfony voicesoftheelephpant mvc tool laravel introduction podcast version composer library series security community update language opinion

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