When trying to optimize a query, I often pull up two query editor windows and try different combinations of JOIN, LEFT JOIN, WHERE, ON, etc.
The execution time at the SQLYog window bottom seems to be a “last Exec time” only. Switching tabs doesn't reflect the query that was run in that tab.
It would be more useful if it were tied to the query tab you're on, then you can run a query. switch tabs. run that query. and flip the tabs back and forth to compare the execution speed.
I realize you could put multiple queries in each tab, but I think it's sufficient to correlate the exec time with the LAST query run in EACH tab. If someone needs to see more exec times, then all they need to do is open more tabs.
The problem is that you can't run a query you just ran a second time, because mySQL has cached the results most likely, so your timing is not accurate. The first time could take 5 seconds, and the second could return in 0.001 second because of this caching. Therefore you have a false sense of optimization.
