Unsupported Screen Size: The viewport size is too small for the theme to render properly.

Schema Browser Not Linked To Query Tabs

forums forums SQLyog SQLyog: Bugs / Feature Requests Schema Browser Not Linked To Query Tabs

  • This topic is empty.
Viewing 4 reply threads
  • Author
    Posts
    • #10561
      gb1071nx
      Member

      I might not be using the right words. “schema browser” is that long panel on the left that has a treeview of all schemas in the current server.

      follow this path:

      Open a particular schema.

      Highlight a table

      click the '3 Table Data' tab, showing contents of the highlighted table

      Now open a new Query tab

      Open a different schema (or the same one, doesn't matter)

      highlight a different table

      click the '3 table data' tab, showing contents of this other table

      Switch back to the first Query tab. What table are you looking at?

      Seeing as how you've done this in a couple seconds, you might remember. But what if you've got 10 tabs open, and it's 6 hours into your work day. Which tab is what table? The schema browser doesn't “scroll to match” (to use an IDE term).

      i'd like it, if when you select the query tab, that the schema browser will scroll and highlight which table's data is being displayed. Or…. put that information *somewhere* on that tab.

    • #25015
      peterlaursen
      Participant

      A Query TAB can contain queries using more than ONE database (actually a single SELECT can).

      It is not possible to 'link' a specific Query TAB to a specific database in the Object Browser.

      I suggest you add a comment at the top like

      — must use some_database

      What you should understand is that the selected database is the latest one one specified with a USE statement.

      When you work on that database you won't need to use full syntax like `database`.`table` ; `table`alone will do.

      I do not see how this request can be implemented.

    • #25016
      gb1071nx
      Member
      peterlaursen wrote on Sep 25 2007, 01:23 PM:
      A Query TAB can contain queries using more than ONE database (actually a single SELECT can).

      It is not possible to 'link' a specific Query TAB to a specific database in the Object Browser.

      I suggest you add a comment at the top like

      — must use some_database

      What you should understand is that the selected database is the latest one one specified with a USE statement.

      When you work on that database you won't need to use full syntax like `database`.`table` ; `table`alone will do.

      I do not see how this request can be implemented.

      But surely, the “3 Table Data” tab is only showing you one database, from one schema, at once? This might be an unfortunate side-effect of combining a sub-tab called “1 Result”, which contains results from the parent query tab that can query any schema and any table (as you say), with a sub-tab called “3 Table Data”, that is limited to one schema/table at once.

    • #25017
      peterlaursen
      Participant

      good point!

      the 'parent' of the DATA tab is the Object Browser.

      the HISTORY tab is 'child' of every Query tab that has been opened since connection was established

      all other TABs have the selected Query TAB as 'parent'.

      Actually .. with hindsight .. it would be more logical if the DATA tab was the 1st/leftmost tab (as close to the Object Browser as possible) and if some graphics clearly indicated this parent/child structure!

    • #25018
      gb1071nx
      Member
      peterlaursen wrote on Sep 25 2007, 02:32 PM:
      Actually .. with hindsight .. it would be more logical if the DATA tab was the 1st/leftmost tab (as close to the Object Browser as possible) and if some graphics clearly indicated this parent/child structure!

      I would still be a bit confused by that. I wonder if it's possible to “promote” the DATA tab to a 'top level' tab. So you'd have 'Query' tabs, with their results at the bottom, but you'd also have DATA tabs named “schema.tablename”, which shows just the data in that table.

      Sorry, I'm going to start 'converging' my two posts. If you did the above, it wouldn't be necessary to link the DATA tab to the Object browser, since you'd know by the tab name, which schema/table you were looking at. That is; whilst flipping between data tabs, you wouldn't need to scroll and re-highlight the Object Browser. Your tab name would suffice.

      Thanks for your thoughts on the matter.

Viewing 4 reply threads
  • You must be logged in to reply to this topic.