By clicking “I agree” below, you consent to the use by us and our third-party partners of cookies and data gathered from your use of our platforms.
The DATE function is useful for assembling dates that need to change dynamically based on other values in a worksheet.
Formulas are the key to getting things done in Excel.
PDF (US Ltr) - 46.7Mb PDF (A4) - 46.8Mb PDF (RPM) - 42.2Mb HTML Download (TGZ) - 10.8Mb HTML Download (Zip) - 10.8Mb HTML Download (RPM) - 9.3Mb Man Pages (TGZ) - 224.9Kb Man Pages (Zip) - 330.3Kb Info (Gzip) - 4.2Mb Info (Zip) - 4.2Mb My SQL Backup and Recovery My SQL Globalization My SQL Information Schema My SQL Installation Guide Security in My SQL Starting and Stopping My SQL My SQL and Linux/Unix My SQL and Windows My SQL and OS X My SQL and Solaris Building My SQL from Source My SQL Restrictions and Limitations My SQL Partitioning My SQL Secure Deployment Guide My SQL Tutorial My SQL Performance Schema My SQL Replication Using the My SQL Yum Repository .
As long as the time zone setting remains constant, you get back the same value you store.
If you store a value, and then change the time zone and retrieve the value, the retrieved value is different from the value you stored.
ts1These problems can be obviated by setting the server timezone to UTC (temporarily, if you prefer), i.e.: SET @old TZ := @@time_zone; SET @@time_zone := ' '; # # Do something with timestamps here; it'll work reliably[*] as everything is in UTC # SET @@time_zone := @old TZ;[*] Actually, not entirely true, as there may also occasionally be leap-seconds, represented by hh: repeating twice.
So events with these timestamps may be more than one second apart, and there isn't a 1-1 correspondence between actual seconds and displayed seconds; and when storing decimal seconds (milliseconds, etc), once again all the local-times-are-out-of order issues can arise.