Upgrading to a misfeature!

[homam]

I'm sorry for being causting, but I can't help it.

Instead of fixing the countless usability flaws in SQLyog, you guys just crippled it even further by forcing the keyboard focus to go to the lower pane with each and every SQL execution.

Now with every SQL statement (even if it was a DDL!!!) the focus just goes away, and you can't type more statements unless you manually move the focus back to the edit pane.

What the hell am I goning to do with the lower pane when I issue SQL DDL? Please think!

Why don't you let the user decide if he wants to move the focus there?

I'm downgrading back to version 4.0.

I just wish that you charged money for SQLyog yet make it even 75% as user-friendly as MS Sql Query Analyzer.

[Ritesh]

I have forwarded your issue to my development team. We will fix this issue in v4.06.

We plan to provide an option in the preference where an user can set his preference for keyboard focus after query execution.

[peterlaursen]

In my view:

SQLYOG is a GUI, that allows for performing most operations without writng sql (the program does), although it is possible to write and edit sql-statements. I think this program behaves like most users of it would expect. So In my view the program behaves logical. But of course I wouldn't mind an option/setting whether the focus should change or not.

Ritesh may have other comments.

Besides I like this forum because there normally is a very kind and polite tone here. That's the main reason why I accepted to become a forum moderator here. Please don't change that!

[peterlaursen]

og, my God …

Ritesh is so damn fast 🙄

[Ritesh]

I believe this is subjective issue.

Many people would like to scroll the resultset using a the keybaord after executing a query. They execute a lot of DML statements and start panning thru the resultset immediately. Probably we could put this as a preference setting. For the time being, use the keyboard shortcut key to bring focus back to editor ( if you dont like using the mouse )

Instead of just mentioning “countless usability flaws”, could you please be more specific? We are committed to make SQLyog the most intuitive and powerful tool for MySQL. Some of your issues could be personal preferences issues and we can have a exhaustive discussion in this forum. On the other hand, some of them could be real usability issues that we might need to address immediately.

[homam]

Ritesh, you can check the usability flaws I mentioned in my recent posts, the most glaring of which is the fact that the window close sequence, Ctrl-F4, is right next to the selected statement execution sequences, Ctrl-F5, and it doesn't even warn the user to save their changes. The window just vanishes. This happened to me more often than I care to remember. I probably use SQLyog on a daily basis more often than most users here.

Another one is not being able to select a cell range, or even a single cell, and copy it to the clipboard in an intuitive manner. Another one is not being able to kill the currently executing statemet; SQLyog just freezes up until the statement is finished up (or you kill the connection manually from MySQL Admin). This isn't how I'd characterize a responsive UI.

As for Peter's GUI comment, I disagree. In the MS SQL Server world, you have a GUI, wizard-like tool (Enterprise Manager) where you can mange your tables and to some degree manipulate your data, and you also have a DBA/Developer-oriented tool to write queries, check their execution plans, create indexes, manipulate tables schemas and their data, etc, and that is Query Analyzer. They're different tools, and each has its own valid uses and scenarios. Neither can substitute the other effectively.

Now SQLyog seems to be trying to play both roles, i.e. a GUI, wizard-like tool AND a DBA/Developer SQL DML/DDL tool. That's fine, as long as it strives to be user-friendly to both audiences.

[Ritesh]

Quote:

the most glaring of which is the fact that the window close sequence, Ctrl-F4

This is again a preferential option.

We used to warn users about unsaved queries till v2.5 but most of our customers at that time found it annoying and we removed it from v2.6 upwards. I think its again an option that can be put as preferences.

Quote:

and copy it to the clipboard in an intuitive manner.

This option has been added in v4.05.

Quote:

SQLyog just freezes up until the statement is finished up (or you kill the connection manually from MySQL Admin).

This feature is one of the important additions in v4.05.

[zzapper]

I always want the best of both worlds, ie powerful GUI, and ability to use CLI commands. I end up writing a lot of mysql manually from within Yog. I think there's a consensus that there should be more support in YOG for this ie Filters etc I'd also love a completion feature on MYSql keywords, Table and field names etc.

Keep up the good work. 😀

[emretemp]

homam wrote on Apr 13 2005, 12:40 AM:

What the hell am I goning to do with the lower pane when I issue SQL DDL? Please think!

Why don't you let the user decide if he wants to move the focus there?

I'm downgrading back to version 4.0.

I just wish that you charged money for SQLyog yet make it even 75% as user-friendly as MS Sql Query Analyzer.

LOL,

at first I thought that smt went wrong, that was a bug or smt like that.

I really cant believe that somoneone there, really changed the focus behavior, in purpose.

just think the main reason of using a gui like sqlyoq. For me main reason is to the write sql commands and execute them. if needed, write another sql command or modify or .. so goes on. Since I can even write the sql results in a file by using sql commands, why would i bother to focus on the results? Am I suppose to change or copy results each time I execute a query? Even if I want to change a spesific row, I can easily do that from sql window. I really cant see any good reason to focus on the result window after executing queries. IMHO focusing result window after executing queries makes sqlyoq totally useless and time consuming. (thats the main reason that i m still using sqlyoq 4.04 🙂 )

as far as i know, all other programs (like azzkicking mssql query analizer) works the same way: if u execute a query, you must keep the focus on the sql window. BECAUSE you may have probably need to change the query string, or modify them or even delete and write a better one or you need an other query to do smt totally different.

IMHO at least you have to give us an option and let us to select the window to focus after executing queries. If you do that, then you can set even object window as default focus selection, I dont care. but jut let me manage my focus window or set it back to sql window.

anyway, at least I want to thank you all, for creating sqlyog v.4.04 🙂

[Author]

Posts