Suggestion: Under the same query console, click the Run button multiple times to execute SQL. The Result tab of the result set will not be automatically replaced.

Under the same query console, the same library or schema name is connected now. When writing multiple SQLs, it is not necessarily necessary to execute them all (mainly a waste of time), so I hope to retain the Result tabs of the result sets of SQLs that have been executed before under the current query console.

In some scenarios, when troubleshooting, data in multiple tables under the same library or schema name will be queried multiple times, and multiple back and forth steps are required. Execute SQL Compare data sets Troubleshoot the problem to find out the possible cause, and then modify the SQL for individual tables Execute SQL again Compare with previously checked data Then troubleshoot the problem to find the cause and modify the SQL … Repeat this for multiple rounds to troubleshoot the problem.

If we distinguish by console, one is to switch the console, which is more troublesome than selecting a SQL statement; and after switching, we need to pay attention to whether the library corresponding to the current console is what we want.

I hope the author can adopt it.

CodePhiliaX / Chat2DB

Suggestion: Under the same query console, click the Run button multiple times to execute SQL. The Result tab of the result set will not be automatically replaced. #1114