RFE: Add Multi Execute window, which propagates and executes its command(-s) to all connected Aliases

[t603]

Hello,

may I ask You to consider following RFE? RFE: Add Multi Execute window, which propagates and executes its command to all connected Aliases.

The reason is for this RFE is to have a (non-?)blocking popup window of New SQL Worksheet called let say "Multi Execute SQL Worksheet", which will not be connected to one particular already connected Alias, but to all already connected Aliases. Then the user will code SQL command(-s) in this "Multi Execute SQL Worksheet" and once the user click Run SQL on selected SQL commands, these SQL command from "Multi Execute SQL Worksheet" will be copied into SQL Worksheet of (all?) already connected Aliases and (immediately or after some "Are You sure to run them on all opened Aliases?" check) executed.

The purpose of this RFE is to enable fast and uniform execution of SQL commands on multiple instances of Aliases, which have the same or similar database objects. Well, some of current features may not be possible (like export to File) unless there will be support of some kind of placeholders inside FileNames like "NameOfAlias", but I guess, that event without such placeholders the "Multi Execute SQL Worksheet" would be an advantage.

This idea is similar to approach of MultiExec feature of MobaXterm vs PuTTY, but in the database world.

This RFE would work the best once RFE #73 and #74 would be implemented, but can work even without them,

Thank You in advance, Stepan

[gerdwagner]

The following was implemented an will be available in future snapshots and versions:

Excerpt from change log:

#75
New function to execute a SQL in multiple Sessions:
The new Session toolbar button "Run SQL in all open Sessions" (ctrl+alt+shift+ENTER)
executes the current SQL in all open Sessions.
The feature can be switched off at menu File --> Global Preferences --> tab SQL
--> checkbox "Allow to run a SQL in all open Sessions"

[t603]

Hello, Gerd,

I tested this functionality and it works OK. But...

I have one more hint. Because Run in all opened Sessions could be very risky operation, I would like to propose:

1. File --> Global Preferences --> tab SQL --> checkbox "Allow to run a SQL in all opened Sessions" should be disabled by default.
2. Each activation (mouse click, keyboard shortcut) of "run a SQL in all opened Sessions" has to be confirmed by some pop-up window with "Are You really sure to run SQL in all opened Sessions" with by default No activated or even check and Yes confirmation. Or even more, to be absolutely sure, the user has to input some short (three digits) random number generated by SQuirreL SQL. My colleagues strongly agreed with me, because without confirmation is a time bomb and without such strong confirmation they would kill me ;-)

Imagine, that You can have opened both testing and production environment opened at one time, so such DROP SQL command can have fatal impact. Current implementation is fully functional but too risky. Moreover "Run in all opened Sessions" button is right next to the "Run all SQLs..." button, so it is just only matter of time, when anyone click accidentally wrong.

Regards, Stepan

[gerdwagner]

The following was implemented and will be available in future snapshots and versions:

Excerpt from change log:

#75
The options "Allow to run all SQLs in editor" and "Allow to run a SQL in all open Sessions"
are now switched off by default. See menu File --> Global Preferences tab SQL.
Note: This change applies only to SQuirreL user directories that did not already
contain these options in their prefs.xml file. The path to SQuirreL's user directory is displayed
in SQuirrel's window title.

[t603]

Hello,

setting two "Run all..." and Run SQL in all..." in Preferences works OK in the latest build. Thank You for it and thank You also for adding the nonrequested first "Run all..." to preferences too. It makes a sense to enable disabling too.

But I would like still to ask for two phase verification dialog: "Are You really sure to run SQL in all opened Sessions" with by default No activated or even check and Yes confirmation. I think that for MultiExec (Run SQL in all...) or "Run all..." it makes me sense to have a confirmation.
In case of "Run all..." one can easily to bypass verification dialog selecting all commands in SQL window and click "Run SQL", which is currently implemented - it is enough, this is already two steps verification now just in other way.

Thank You, Stepan