Feature Request: Single Connection, Multiple Queries, Multiple Databas

[GTC]

I often am working in multiple databases on the same server, and love and use the multiple query tabs for the pieces I am working on.

However, the active database context is controlled at the Connection level, rather than the Query Tab level. As a result, I often attempt to execute SQL statements against the wrong database.

A query tab should be linked to a specific database, and, perhaps, even move the database drop down list to the query tab controls.

In a radical UI change, you could actually move the DB Object Browser tree into the Query tab. Then the queries and active context would be linked (similar to http://code.google.com/p/sqlyog/issues/detail?id=1497), and you'd change database context by clicking on the database in the object browser, This would completely eliminate the database drop-down list, which in reality is redundant when you have the object browser. This approach would also mean that, contextually, the objects I'm working on in the query would/could be visible, rather than showing whatever I happened to have clicked on last in some other query tab.

[peterlaursen]

Let us see if you get any responses to your poll.

But this is both correct and incorrect actually “.. the database drop-down list, which in reality is redundant when you have the object browser”. It is there for two reasons

1) Historical reasons. (in this context your statement is correct).

2) User may hide the Object Browser (from 'edit' menu or Ctrl+Shift+1) (in this context your statement is incorrect).

[GTC]

'peterlaursen' wrote:

Let us see if you get any responses to your poll.

But this is both correct and incorrect actually “.. the database drop-down list, which in reality is redundant when you have the object browser”. It is there for two reasons

1) Historical reasons. (in this context your statement is correct).

2) User may hide the Object Browser (from 'edit' menu or Ctrl+Shift+1) (in this context your statement is incorrect).

True… perhaps the aggregation of my suggestion would be a database drop down that is part of the tab or tool-strip under the tab, and the object browser would limit itself to the child nodes that currently appear under the database name.

[peterlaursen]

Actually your request conflicts with another popular request: that there should be only one Object Browser for all open connections.

[TerryN]

Haha. Wow, I didn't realize I was about to single-handedly split the ticket with my vote. 😀

I'm trying to see myself working this way, but just can't because of the current behavior of having all tabs in a connection be locked up while any one of them is executing. 🙁

I'd just open another connection. Using Ctrl-Tab it's a breeze to switch between them–actually easier than switching between tabs, I think. Since under what you're proposing, those multiple queries couldn't be executing simultaneously anyway, presumably your work pattern isn't such that they'd be returning data simultaneously if put in separate connections (though they'd be able to).

Are you limited to one connection by the server? Do you need them to share user variables? Or are you manually tunneling, so an additional connection is a hassle?

[peterlaursen]

You can have multiple connections to the same server.  Each connection will create its own 'session' and as user variables have a session-scope they are not shared between connections. This does not have much to do with SQLyog really – this is how user variables are implemented in the server.

[Author]

Posts