Toad World® Forums

Change connection of all tabs


#1

Hi all,

say I have 10 editors open, which are connected to the development server.
Now I am done with that server, and I want to work with them on the test
server. Is there a way to change connections of all tabs, instead of
“right-click -> change connection” on all the tabs?

Version 5.0.0.250

Thanks
Ercan


#2

Ercan, I agreed with you need, but I see security issues here because I mix and
match development servers connections which is a matter of style. The whole
color thing with connections allow user to keep the connections straight…

If they want to implement what you have suggested, I am good with that as long
as it does not change the current default behavior.

Therefore, I support your idea of “Change all connections to “ as a
separate icon type action.

Hank Freeman

Senior Systems, Database/Data Warehouse Architect

hfreeman@msn.com

678.414.0090 my cell Primary
image001.gif


#3

Ercan, I agreed with you need, but I see security issues here because I mix and
match development servers connections which is a matter of style. The whole
color thing with connections allow user to keep the connections straight…

If they want to implement what you have suggested, I am good with that as long
as it does not change the current default behavior.

Therefore, I support your idea of “Change all connections to “ as a
separate icon type action.

Hank Freeman

Senior Systems, Database/Data Warehouse Architect

hfreeman@msn.com

678.414.0090 my cell Primary
image002.jpeg


#4

What if we used an interface similar to the “Group Execute” feature. That would allow you to choose all editors or a selection of editors. I would LOVE to have something like that available.


#5

Ercan, we will try to figure out with this interesting request in the next release. I’ve created ST74276 for this request.

Hank, for sure we don’t want to broke current behaviour.


#6

Ercan, we will try to figure out with this interesting request in the next release. I’ve created ST74276 for this request.

Hank, for sure we don’t want to broke current behaviour.


#7

We have discussed this request and here the answer: its dangerous to have it work like this. We used to have it work this way but changed it per request due to performance and other issues.


#8

We have discussed this request and here the answer: its dangerous to have it work like this. We used to have it work this way but changed it per request due to performance and other issues.

Message was edited by: Alexander Maximov


#9

Alexander, I would really like more details on why you have made this statement.
From where I sit, the benefit may be there, so please explain !

@Alexander::

We have discussed this request and here the answer: its dangerous to have it
work like this. We used to have it work this way but changed it per request due
to performance and other issues.

Hank Freeman

Senior Systems, Database/Data Warehouse Architect

hfreeman@msn.com

678.414.0090 my cell Primary
image001.gif


#10

Alexander, I would really like more details on why you have made this statement.
From where I sit, the benefit may be there, so please explain !

@Alexander::

We have discussed this request and here the answer: its dangerous to have it
work like this. We used to have it work this way but changed it per request due
to performance and other issues.

Hank Freeman

Senior Systems, Database/Data Warehouse Architect

hfreeman@msn.com

678.414.0090 my cell Primary
image002.jpeg


#11

Here is the danger:

  1. Have the editor open with a script that you are working on with your
    development database.

  2. Close the development connection.

  3. Open a connection to the production database.

  4. Open up the development connection again.

  5. Execute the script in the editor from step one.

With our current implementation this will execute the script on the development
connection. With the previous (Or suggested new behavior) this would execute the
script on the production database since that was the first connection opened
after the editor was “orphaned” from its connection.

/Mauritz
image002.jpeg


#12

Here is the danger:

  1. Have the editor open with a script that you are working on with your
    development database.

  2. Close the development connection.

  3. Open a connection to the production database.

  4. Open up the development connection again.

  5. Execute the script in the editor from step one.

With our current implementation this will execute the script on the development
connection. With the previous (Or suggested new behavior) this would execute the
script on the production database since that was the first connection opened
after the editor was “orphaned” from its connection.

/Mauritz
image001.gif