Your message dated Wed, 08 Sep 2010 13:18:34 +0300
with message-id <[email protected]>
and subject line Closing very old Mysqld bugs
has caused the Debian Bug report #368534,
regarding Partial wrong results of function SEC_TO_TIME
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
368534: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=368534
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: mysql-server
Version: 4.0.24-10sarge1
The function sec_to_time delivers partly wrong results from calculated
arguments. Here are some examples:
mysql> select sec_to_time(69);
+-----------------+
| sec_to_time(69) |
+-----------------+
| 00:01:09 |
+-----------------+
1 row in set (0.01 sec)
-> This is correct.
mysql> select sec_to_time(69 / 100 * 100);
+-----------------------------+
| sec_to_time(69 / 100 * 100) |
+-----------------------------+
| 00:01:08 |
+-----------------------------+
1 row in set (0.00 sec)
-> This is obviously wrong.
mysql> select sec_to_time(68 / 100 * 100);
+-----------------------------+
| sec_to_time(68 / 100 * 100) |
+-----------------------------+
| 00:01:08 |
+-----------------------------+
1 row in set (0.00 sec)
-> This is correct.
mysql> select sec_to_time(67 / 100 * 100);
+-----------------------------+
| sec_to_time(67 / 100 * 100) |
+-----------------------------+
| 00:01:07 |
+-----------------------------+
1 row in set (0.00 sec)
-> Correct.
mysql> select sec_to_time(62 / 100 * 100);
+-----------------------------+
| sec_to_time(62 / 100 * 100) |
+-----------------------------+
| 00:01:01 |
+-----------------------------+
1 row in set (0.00 sec)
Wrong again. But when I do the following (which is of course
mathematically the same):
mysql> select sec_to_time(62 / (100 / 100));
+-------------------------------+
| sec_to_time(62 / (100 / 100)) |
+-------------------------------+
| 00:01:02 |
+-------------------------------+
1 row in set (0.01 sec)
The result is correct again.
I am using Debian 3.1 (i386) with kernel 2.4.27 and libc6
2.3.2.ds1-22sarge3.
Nils
--- End Message ---
--- Begin Message ---
Version: 5.0.5beta-1
This bug was reported back when the bts didn't have version tracking, and the
maintainer apparently forgot to close this bug when etch was released.
The maintainer claims in the bug report log that this has been fixed in
upstream Mysql 5.0. The first 5.0 series upload to unstable was 5.0.5beta-1.
--
Arto Jantunen
--- End Message ---
