No subject

Wed Dec 10 08:32:44 UTC 2008

http://dev.mysql.com/doc/refman/5.0/en/time-zone-leap-seconds.html
<http://dev.mysql.com/doc/refman/5.0/en/time-zone-leap-seconds.html>

9.7.2. Time Zone Leap Second Support

Before MySQL 5.0.74, if the operating system is configured to return
leap seconds from OS time calls or if the MySQL server uses a time zone
definition that has leap seconds, functions such as NOW() could return a
value having a time part that ends with :59:60 or :59:61. If such values
are inserted into a table, they would be dumped as is by mysqldump but
considered invalid when reloaded, leading to backup/restore problems.

As of MySQL 5.0.74, leap second values are returned with a time part
that ends with :59:59. This means that a function such as NOW() can
return the same value for two or three consecutive seconds during the
leap second. It remains true that literal temporal values having a time
part that ends with :59:60 or :59:61 are considered invalid.

--------------010606070302060801060003
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
</head>
<body bgcolor="#ffffff" text="#000000">
<script type="text/javascript">
            function sendMeTooForm(e) {
                $('affectsmetooform').submit();
                e.preventDefault();
            }
            function connectMeTooLink() {
                var me_too_link = getFirstElementByTagAndClassName(
                'a', 'menu-link-affectsmetoo');
                connect(me_too_link, 'onclick', sendMeTooForm);
            }
            registerLaunchpadFunction(connectMeTooLink);
        </script>
<div id="bug-description">
<p>From the MySQL manual:</p>
<p><a rel="nofollow"
 href="http://dev.mysql.com/doc/refman/5.0/en/time-zone-leap-seconds.html">http://<wbr>dev.mysql.<wbr>com/doc/<wbr>refman/<wbr>5.0/en/<wbr>time-zone-<wbr>leap-seconds.<wbr>html</a></p>
<p>9.7.2. Time Zone Leap Second Support</p>
<p>Before MySQL 5.0.74, if the operating system is configured to return
leap seconds from OS time calls or if the MySQL server uses a time zone
definition that has leap seconds, functions such as NOW() could return
a value having a time part that ends with :59:60 or :59:61. If such
values are inserted into a table, they would be dumped as is by
mysqldump but considered invalid when reloaded, leading to
backup/restore problems.</p>
<p>As of MySQL 5.0.74, leap second values are returned with a time part
that ends with :59:59. This means that a function such as NOW() can
return the same value for two or three consecutive seconds during the
leap second. It remains true that literal temporal values having a time
part that ends with :59:60 or :59:61 are considered invalid.</p>
</div>
</body>
</html>

--------------010606070302060801060003--