Bug/feature: Common Table For Each 'query' Tab

[Jason O'neil]

How to reproduce:

1) open two 'Query' tabs (and 'Table Data' inner tab);

2) in 1st tab open some table (tblA);

3) in 2nd tab open another table (tbl:cool:;

4) go back to 1st tab, and switch inner tab from 'Table Data' to any other – current table for 1st 'Query' tab is tabB.

It also produces a bug – if we set some filter in 1st tab on step 2), after 4) and switching to 'Table Data' we have error – filter in 1st tab from tabA is applied to tabB.

[peterlaursen]

Please tell the SQLyog version you are using.

[Jason O'neil]

'peterlaursen' wrote:

Please tell the SQLyog version you are using.

v9.20

[ashwin]

Hi Jason O'neil,

Common Table For Each 'query' Tab is not a bug actually, it is by design. Whichever table you choose in the Object browser you will be viewing the same in the table data across different query tabs. But there is a request to make data tab 'sticky'. Refer: http://code.google.com/p/sqlyog/issues/detail?id=1574

Quote:

It also produces a bug – if we set some filter in 1st tab on step 2), after 4) and switching to 'Table Data' we have error – filter in 1st tab from tabA is applied to tabB.

This is a bug. Filter should be reset after you switch back to the query tab1. I have added this issue in our issue tracker here: http://code.google.com/p/sqlyog/issues/detail?id=1681

[peterlaursen]

I would express same a little differently.

1) There is no correlation between DATA tab and QUERY tabs. The DATA tab (there is only one possible a a time currently) will always display data from the currently selected table in OB. In other word a DATA tab is not 'inner' (or 'child') to a QUERY tab at all. On the opposithe the DATA tab is 'child' of the Object browser selection.

2) There is however a correlation between QUERY tabs and RESULT tabs (but no between Object Browser and RESULT tabs). If you execute query(-ies) from a QUERY tab a RESULT tab will open for each query that returns a resulty set. Every open QUERY tab may have multiple RESULT tab 'children' that become visible by selecting the QUERY tab ('parent') it belongs to.

I don't agree that there is a bug here (but maybe I do not understand). A filter has been set for a specific DATA tab and it is active for same untill it has been changed/reset. Operations in Query tabs have no and should have no effect on filter settings on DATA tab level.

You may have a point that displaying the DATA tab in the same area as RESULT, MESSSAGE tabs could give the impression to user that DATA is 'child' of QUERY. But same would apply to INFO and HISTORY tab as well. DATA and INFO are derived from Object Browser selection, HISTORY tab is global, and RESULT and MESSAGES tabs are 'children' of QUERY tab. This design was chosen simply in order to utilize the available space on screen as much as possible.

[Jason O'neil]

I don't insist it's a bug, but is a bit inconvenient with current window composition – if I want to view the History/Info/Table Data – I need to create a Query tab. I'm not even telling that if you close your last Query tab – history will be completely lost.

Those tabs are dependent on Query tab – that's what i mean 'inner'.

[peterlaursen]

Good point here. It is possible to close all all Query Tabs (as long as a single Data Search, Query Browser or Schema Desinger tab is left open)..

Actually we side-by side display

* global information (HISTORY)

* information that is 'child' of a QUERY tab in the above pane (RESULT, MESSAGES)

* information that is 'child' of Object Browser selection (DATA, INFO)

We have had some discussions about this before (with users and internally). Most users seem happy with the organization even if it is not logically correct. And providing 5 panes instead of 3 would be an annoyance for users with small monitors (small laptops, netbooks). But could make sense wiht laarge resolutions. So we just did not find a better solution yet working for all.

[Jason O'neil]

I suppose, the simplest solution is

1. Make some “unclosable” tab Global in the second window – if it's active, it has 3 global/OB tabs – History/Info/Table Data.

2. Attach to each Query his “child” tabs (History/Data/Info/Messages/Result) just like it is now.

[peterlaursen]

After I discussed with Ashwin I now understand what the bug is here!

[ashwin]

Hi Jason,

We will fix the filter reset bug in the next public release.

And, We have decided to move data tab, info tab, history tab to the query tab level as they are not dependent on the query tab. This has been added here: http://code.google.com/p/sqlyog/issues/detail?id=1682

We will inform you once we this has been implemented.

Thanks,

Ashwin A

[Jason O'neil]

'ashwin' wrote:

Hi Jason,

We will fix the filter reset bug in the next public release.

And, We have decided to move data tab, info tab, history tab to the query tab level as they are not dependent on the query tab. This has been added here: http://code.google.com/p/sqlyog/issues/detail?id=1682

We will inform you once we this has been implemented.

Thanks,

Ashwin A

Thanks a LOT! Especially for a non-delay support and feedback!

[Author]

Posts