A Few Ideas

[lenochware]

Thanks for this great application. I have a few ideas (regarding UI) however:

-I would like arrows back/forward (similar to undo/redo) besides sql query window, so I could go back to history of executed queries.

I know that there is tab “history”, but this seems more handy to me.

– In function copy “database to different host” is just dropdown for db-selection. I have a lot of db

and this is rather dificult and confusing go to proper db. Also this is sensitive operation, so

I think that interface should be more clean. Some kind of tree with host/database levels, or even possibility

choose copying to the database selected in another tab would be great.

– Sometimes I need copy only few rows from the result set/table to the different host.

At now, I must export sql-dump and import into another host. Some better way would be cool.

My idea for improvement is possibility export sql-dump to the clipboard optionally, so I could avoid working with file…

– And last little thing: I would like possibility sort “fieldname” column in alter table dialog.

Because in tables with many columns ocassionally I am looking if some field exists, or check its name, and it is difficult to find it

now.

Sorry if some of that things are already done or in todo. 🙂

And thanks again – sqlyog is the best!

[peterlaursen]

Thanks for this great application. I have a few ideas (regarding UI) however:

-I would like arrows back/forward (similar to undo/redo) besides sql query window, so I could go back to history of executed queries.

I know that there is tab “history”, but this seems more handy to me.

>> You can multiple queries in one query tab. Also if you have multiple query tabs in one connection. In HISTORY there is no record of from what query tab a statement was executed. It may be a tab that has been closed. And also HISTORY logs quereis that were not written in the editor but executed due to GUI operations. I can't see that this is possible – HISTORY has no track of *where did it come from*. But you can use standard windows shortcuts like ctrl+z to recover old contents in a query tab (and ctrl+y to spool forward)

– In function copy “database to different host” is just dropdown for db-selection. I have a lot of db

and this is rather dificult and confusing go to proper db. Also this is sensitive operation, so

I think that interface should be more clean. Some kind of tree with host/database levels, or even possibility.

>> Currently we use the 'connection name' as defined in SQLyog. You can use prefixes and suffixes in the connection name. Also you can specify specific dtabases in the connection settigns

choose copying to the database selected in another tab would be great.

>> This I would find unsafe. I think that user should explicitly select. Automatics could be a big surprise for users. Could you elaborate the logic if a user has 5 or 10 connections open? Maybe display the open ones on top of the list?

– Sometimes I need copy only few rows from the result set/table to the different host.

At now, I must export sql-dump and import into another host. Some better way would be cool.

My idea for improvement is possibility export sql-dump to the clipboard optionally, so I could avoid working with file.

>> Export to clipboard is an old request: http://code.google.com/p/sqlyog/issues/detail?id=99. I agree that this is probably overdue now. I think we should pay attention to it. But every developer is busy for at least one to two weeks

– And last little thing: I would like possibility sort “fieldname” column in alter table dialog.

Because in tables with many columns ocassionally I am looking if some field exists, or check its name, and it is difficult to find it now.>> Having the columns in another order in that dialog than in the database/table would be a problem . It would generate and ALTER TABLE .. REORDER COLUMNS when saving. Also that dialog weill be compeltely redesigned in next maajor version (9.4), but same considerations would apply to both old and new version.

[lenochware]

>> You can multiple queries in one query tab. Also if you have multiple query tabs in one connection. In HISTORY there is no record of from what query tab a statement was executed….

I am not saying that it should be based on current history tab. Perhaps some new history connected to sql-query window, with queries executed from this window? In my work, I am often jumping between 3-6 queries, so I am searching for most comfortable way…plus back/forward is common concept, which anyone immediately understand. I know about other ways – multiple tabs and multiple queries in one window, but this seems better to me.

>> This I would find unsafe. I think that user should explicitly select. Automatics could be a big surprise for users. Could you elaborate the logic if a user has 5 or 10 connections open? Maybe display the open ones on top of the list?

Yes, or make it highlighted or so. I have typically open database to which I want copy into other tab, so if other people do it same way, it would be clever to offer this database for copying – at least I think so.

>> Having the columns in another order in that dialog than in the database/table would be a problem . It would generate and ALTER TABLE .. REORDER COLUMNS when saving. Also that dialog weill be compeltely redesigned in next maajor version (9.4), but same considerations would apply to both old and new version.

Yes, you are true, if I add/remove column in the dialog and do sorting, it would be probably confusing…it seems like bad idea, forget it.:)

[lenochware]

Or offer preselected database for copying only in case there are opened only two tabs…

[peterlaursen]

1)

Step back/forward:

Actually I find ctrl+z and ctrl+y the most standard to step back and forwards in a 'text view' of any kind.. It is there (we did not code it – the Windows API provides it for free with its text controls). Even when you write in this Forums you can use these and in web forms in browsers you can use it, In any texteditor, wordprocessor, in a cell in a spreadsheet etc. So some GUI controls actually calling it would probably not be a problem. But I really don't find a proper place to put it without wasting space. Where could you propose?

But this will of course 'spool'/step what was typed and not what was executed.

2)

Better overview of connections listing: I have added this to our issue tracker: http://code.google.c…/detail?id=1726

We also have discussed before to move the connections setting out of the SQLyog.ini file (would then probably be to a SQLite database) in order to sort and filter in the connections manager. That would also be used in the context here. Another option could be an option to add 'tags' to connections.

This is not a new discussion. But it has not been priority till now.

[lenochware]

1)

Step back/forward:

Well, I would like back/forward in what was executed, not plain undo/redo.

But maybe there can be problem, if there will be more than one queries in the editor…

It could be into the toolbar, I suppose – similar to internet browser back/forward.

Or I have yet another idea: improve history tab with possibility to hide “system” queries and copy sql code into editor when

I doubleclick on line in history.

Even without filtering feature “copy sql query from history-tab to editor with one click” would be nice, imho. Maybe better than back/fw buttons.

2) Thanks.

[peterlaursen]

Currently we just save HISTORY in memory basicaly like a palin text file. We do plan to save to a file with some rotation system. The file format for this would probably also be a SQLite database. That would give us an option to save some meta-information. Like whether this was a user query or an generated query SO let us consider in this context.

[peterlaursen]

added here http://code.google.com/p/sqlyog/issues/detail?id=410

[Author]

Posts