Saving Viewed Tables By Tab

[Frizzled]

Hi Webyog team!

I've been using SQLyog for years and ever since tabs were added there's been a behavoir that's been a real pain. When you have multiple tabs open, SQLyog does not save the table you're viewing by tab, it saves the last table viewed (regardless of tab) and uses that globally whenever you switch between the “Results” view and “Table Data” view.

For example, if you have two tabs open each view a different table in Table View, you run a SQL query in the first tab (say you want to look at some specific areas of that Table View), this changes you to Results view in that tab, then you switch to the second tab and pull-up a different table (by clicking on it from the list on the left). Now when you switch back to the first tab, and click on “Table Data” it will take you to the table you just pulled up in the second tab, instead of the table this tab was originally on.

I always thought of tabs as individual workspaces … why are the Data Views linked like this? I encounter this behavoir many, many times each day and it's always a little frustrating.

_f

[Aparna]

Hi,

Well as i understand depending on the tab you focus you want the table data tab to display that particular table and not the last viewed table ???

As now when there are multiple Query tabs, the table data tab displays the last selected table irrespective of which Query tab you move to.

Please correct me if i am wrong.

Regards,

Aparna

[Frizzled]

'Aparna' wrote on '24:

when there are multiple Query tabs, the table data tab displays the last selected table irrespective of which Query tab you move to.

Correct, you can best see this behavior if you switch between Results (after running a query) and Table Data views on different tabs. The tabs do not save which Table Data view they were using, they will all use the last Table Data view you looked-at.

_f

[Aparna]

Hi,

Completely agree that this is confusing and a little annoying sometimes. But let us consider this scenario. Suppose each query tab has a query that belongs to tables present in different databases then to ensure that the table data tab shows the tables accordingly a “USE DB” statement needs to be fired every time you navigate between the tabs and it is not feasible. This was considered earlier but then due to the problems with implementation was not taken up. Feel free to give your suggestions regarding this if any.

Regards,

Aparna

[Frizzled]

Sorry for the late response, I dropped in while debating another year's subscription –

I think I understand why this working this way now: to save USE DB calls you are assuming the last table clicked (in any tab) is always the current table. This assumption was fine before tabs were added to SQLYOG, but with tabs you have an application that is begging for multi-tasking (it's kind-of the whole point of having different tabs), but you have a program that still has a single task mind-set.

How about having SQLYOG remember the used database by tab, then compare the database it's supposed to run the current query on in the active tab with the database of the last query (in what-ever tab that was)? If the databases match you've saved a USE DB call, if they don't just throw one in.

… OR (even easier) save each current table in Table Data by Query tab then always run a USE DB call, but *only* when the user switches away from Table Data and back again (ie. they run a statement, then want to go from Results back to Table Data).

I suppose all this is moot, years ago (literally) I asked that Shift+Click reverse sort fields in Table View and was told that was going in with the next build (I think that was in version 5 or 6) … with that not in yet I'm not going to hold my breath on this issue 😉

_f

[peterlaursen]

There is a missunderstanding here: “but with tabs you have an application that is begging for multi-tasking (it's kind-of the whole point of having different tabs)”.

Different Query tabs use same connection and thus same program thread. Different Connection tabs (obviously) use different connections and different program threads. It you want to 'multitask' to the same server open more than one connection.

[peterlaursen]

Just one more thing I forgot to mention (it may be trivial for you or you may not know it – I can't tell).

The MySQL client-server protocol has no option for 'parallellism'/''multitasking'. When a client instance sends a query to the server it can only do one thing: wait for the server response. 'parallellism'/''multitasking' from an application requires multiple connections from different client instances invoked by the client application. There is no other way with MySQL.

[Author]

Posts