Transferring active connection when opening a new SQL file

[Benjin]

Pull Request Template – vscode-mssql

Description

Fixes #19477

Automatically transfers connection from the active SQL file to a newly-opened SQL file.

Code Changes Checklist

• New or updated unit tests added
• All existing tests pass (npm run test)
• Code follows contributing guidelines
• Telemetry/logging updated if relevant
• No regressions or UX breakage

Reviewers: Please read our reviewer guidelines

[github-actions]

PR Changes

Category	Main Branch	PR Branch	Difference
Code Coverage	59.26%	59.19%	⚪ 0.00%
VSIX Size	15359 KB	15375 KB	⚪ 16 KB ( 0% )
Webview Bundle Size	3712 KB	3712 KB	⚪ 0 KB ( 0% )

[richardtallent-erm]

I'm glad to see this here, since it seems to be related to my issue (#19477)! However, the way this code seems to be set up (and I freely admit ignorance of the VSC codebase), it's unclear what would happen if a new tab were opened while a query is pending or running in the existing tab.

It's fine to transfer connections when there is no active query work going on. But if I have a query pending or running in Tab 1 and I open an SQL file creating Tab 2 (or just open a new query tab), I would want my query to continue running in Tab 1 and show its results there, but I would also want Tab 2 to auto-connect to the same database fluently. Ideally in a way that doesn't make me pause my work to wait for it to connect or update IntelliSense in order to run the new query. And certainly in a way that doesn't require me to manually choose the connection again (the current state).

[aasimkhan30]

@richardtallent-erm ,
The way this code works, it doesn’t reuse the exact same connection between files. Instead, it gets the connection credentials and establishes a new connection for the new file.

As a result:
• Each file is connected independently.
• Ongoing queries in the original file won’t be interrupted.
• Disconnecting one file won’t affect the other; the second file remains connected.