Creation of a database connection pollutes project repository

[aledomu]

Is your feature request related to a problem? Please describe.
Every time I set up a new connection, the settings are stored in the .vscode folder in the project repository I'm working on. I cannot use this extension with this policy.

Describe the solution you'd like
Ask where to store the connection settings and, in case of choosing the user settings, if it should be synchronized or not.

Describe alternatives you've considered
Use DBeaver and deal with moving code and files around.

[gjsjohnmurray]

Possible workaround is to close your workspace before setting up the connection. This should cause it to get created in your settings.json. Then open the workspace. You will be able to use it, and if you edit its definition the changes should get filed in your settings.json.

[jonasbjoralt]

+1 to this issue. We have a multi-workspace setup, so connections were stored in the shared workspace.
That's nice for local databases by all means, but it's a deal-breaker for production-databases