[gb1071nx]

peterlaursen wrote on Sep 25 2007, 02:50 PM:

no .. not wrong. There are always PROs and CONs with any GUI design.

In terms of SQL implementation we would then have to send a USE statement when a specific Query tab is clicked. That could be done, and we could relatively easy implement some kind of a 'properties' dialogue for a Query tab.

For what it's worth, using Wireshark, I see that DBManager issues something like that (I don't see “USE”, but I see the schema name) only when a query is run, not on a tab change. But that's an implementation detail.

peterlaursen wrote on Sep 25 2007, 02:50 PM:

We should then optimally as well change the display of the selected database in

* the dropdown where selected database displays

* the Object Browser

when a Query tab is clicked.

It should *definitely* change the drop-down. In prior versions of DBManager, this didn't always happen, and it was a bad, bad bug. You were never sure what schema you were really on. Object browser: I'd speculate it's not as important, IFF the drop-down is guaranteed to be 'correct' and to 'win'. The object browser is then just a way to navigate to, and open, new Query tabs ( and/or Data tabs; see my other post), but it doesn't have to frantically scroll and re-highlight to “keep up” with you flipping between tabs. I'd almost count that as a distraction.

peterlaursen wrote on Sep 25 2007, 02:50 PM:

If you noticed: when you select in OB the dropdown changes, but when you select in dropdown OB display does not (it is the dropdown that 'counts')! There are some coding difficulties here that have not been solved. If a Query tab should SIGNAL change-of-database to the other GUI elements then it get even more complicated. But of course complications is no excuse!

I think we will need to discuss this! We will relase 6.1 beta 1 shortly and after that we can get some air for discussing new ideas.

Thanks again for your thoughts on this. And apologies to repeated references to “the other guys”. 🙂

[gb1071nx]

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.

[gb1071nx]

Yes, my other topic *looks* the same, but isn't quite.

On this one then:

DBManager doesn't “restrict” in the sense that if you typed “SELECT * FROM schema.tablename” into a tab that was currently on some schema != to the one specified in the SELECT.. it will still work as expected. You can do cross-schema SELECTs and all that, or a simple select from one schema, which happens to be different from your currently selected schema in the drop-down…

But what it *does* allow you to do (which IMO is not 'wrong') is select the (if you will) “default” schema for that tab, and then simply type “SELECT * FROM tablename”. And it allows you to set a different default for different tabs.

Do you feel that's “Crazy” and “wrong” ?

[gb1071nx]

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.

[Author]

Posts