tags 368534 + confirmed wontfix thanks Hello
On 2006-05-22 BSV Fehmarn-Rund wrote: > The function sec_to_time delivers partly wrong results from calculated > arguments. Here are some examples: That's true, even for MySQL 4.1, but has been fixed in 5.0. You could get the packages from Etch/Sid as Sarge backport from www.backports.org. As Sarge may not receive updates except for really critical bugs, this one will never be fixed. I leave it open for reference to other users, though. bye, -christian- > 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. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
