Bug #14946 | BENCHMARK() function returns strange results for stored functions | ||
---|---|---|---|
Submitted: | 15 Nov 2005 13:11 | Modified: | 2 Feb 2006 13:58 |
Reporter: | Beat Vontobel (Silver Quality Contributor) (OCA) | Email Updates: | |
Status: | Duplicate | Impact on me: | |
Category: | MySQL Server: Stored Routines | Severity: | S3 (Non-critical) |
Version: | 5.0.15-standard-log-i686-glibc23 | OS: | Linux (SuSE Linux 2.4.21-273-smp4G) |
Assigned to: | CPU Architecture: | Any |
[15 Nov 2005 13:11]
Beat Vontobel
[15 Nov 2005 13:47]
MySQL Verification Team
Thank you for the bug report.
[15 Nov 2005 14:57]
Beat Vontobel
I've just seen this forums post from Felix Geerinckx in the discussion on this bug. He experienced a similar difference in execution times of stored functions versus inline code between SET and UPDATE statements: http://forums.mysql.com/read.php?98,54177,54654#msg-54654 This could be related and probably mean that this is not a BENCHMARK()-only problem but could be somewhere deeper.
[2 Feb 2006 13:48]
Jon Stephens
Please do not submit the same bug more than once. An existing bug report already describes this very problem. Even if you feel that your issue is somewhat different, the resolution is likely to be the same. Because of this, we hope you add your comments to the original bug instead. Thank you for your interest in MySQL. Additional info: Marked this as a duplicate of Bug #15014.
[2 Feb 2006 13:58]
Beat Vontobel
> Please do not submit the same bug more than once. An existing > bug report already describes this very problem. [...] Because of > this, we hope you add your comments to the original bug instead. Hi Jon, thanks for your friendly note, but I couldn't add my comment to the original bug, as this one was the original, just look at the dates. ;-)