Hi,

I've been using SQLYog community version for a while now, great too. I noticed today that the time indicator in the status bar at the bottom can be way off. I ran a query in SQLYog and it reported a duration of 1700 ms even though it seemed to take much longer (didn't measure with stop watch). Using the mysql client I confirmed the same query actually takes about 30 seconds.

I depend on these time indicators to tell me if I'm making progress when attempting to optimize my queries. Is there a known problem with this? I'm using 7.02, the same problem occurred in a 6.x version I used earlier today before upgrading to the latest stable one.

In another extreme case I had SQLYog report the query took 4000 ms to complete when really it was more like 4 minutes.

Thanks,

Sander

Did you read this:
http://webyog.com/faq/content/8/147/en/how...g-gives-me.html

??

Hi,

I didn't before but now I did. So the answer is that the status bar shows how long it takes between submitting the query and finishing the execute. In my case I guess it takes minutes to transfer the data. Not very intuitive to show the execute time rather than complete time spent.

Thanks,

Sander

You can search the Forums here and you will find similar discussions!

When we changed last time we asked users, but had very little feedback. But I agree that it is not very intuitve. We also have a few more releated requests like

* 'in progress' time indicator
* formatting hh:mm:ss:xxx

OK .. we discussed this and realize that our presentation is not good enough (the logic is however).


So will will fix this before 7.1 FINAL release. We do not consider it an emergency, so developers will finish what they have started. I think we can start on this around Monday. I propose:

HISTORY tab: no change
MESSAGES tab: exec: <time1>, transfer: <time2>, total: <time3>
status bar: <time1>/<time3>. If there is room for it some text too!


All times will be formatted hh:mm:ss:mss.
And of course it will still be based on TIMESTAMPS collected on client machine (because that is the only way)

As regards the request to display 'on the fly time' I do not think we can do this this time. It will require a seperate thread (similar to the thread that displays the 'red cross' STOP icon while a query is running). This is no principal difficulty however - only quite a lot of work!



There is still time for anybody to comment and propose!

Thanks Peter for your attention to this matter. I admit I didn't search the forum, sorry. I will do so next time. I like your proposal. A running clock is not needed IMO.

Thanks for providing such a great tool for all of us to use!

Best,

Sander

Yup, that pretty much sums up the issues in the current version.

Note that I personally would get a *lot* of value from a 'running clock' in the status bar.
I often execute long queries, and seeing/knowing how long the current query has been executing provides a lot of value
-in some cases I can estimate how long I'll have to wait for results
-in some cases it tells me I better forget about it and try to get the results using a different query