Bug #69840 SQL Query Duration Appears incorrect
Submitted: 25 Jul 2013 19:57 Modified: 4 Sep 2013 18:49
Reporter: Mike Reid Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S2 (Serious)
Version:6.0.4 BETA3 OS:MacOS (10.8.4)
Assigned to: CPU Architecture:Any
Tags: duration, fetch time, query time

[25 Jul 2013 19:57] Mike Reid 
Description:
Running SQL in  v6.0.4 BETA3 no longer reports the query duration / fetch time correctly. It always returns "0.000 sec" for fast queries, and looks incorrect for longer running queries (e.g. 0.002 sec for something taking multiple seconds) 

How to repeat:
1. Install latest 6.0.4 BETA3 Workbench
2. Run any SQL statement, preferably one short and one long running query.
3. See the duration reported as taking 0.000 sec, or very similar event for long running queries.

Suggested fix:
Double check the duration calculation conversion from ms to seconds. Something definitely appears to be off.
[26 Jul 2013 14:43] Alfredo Kojima 
I can confirm, thank you for reporting this.
[2 Aug 2013 16:25] Mike Reid 
This appears to have been corrected in the latest 6.0.5 BETA. Can anyone else confirm?
[4 Sep 2013 18:49] Mike Reid 
Closing, appears to have been corrected.
[27 Sep 2013 3:29] Philip Olson 
Fixed as of MySQL Workbench 6.0.5, and here's the changelog entry:

The "Query duration / Fetch time" report failed to function properly.

Thank you for the bug report.