You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
On the previous Postgres driver there was an option to store the credentials in userspace vs the workspace. This option is no longer available, which causes some odd conflicts when connections are already stored there.
I would not be surprised if #567 is coming from this issue.
For instance, I can create a userspace connection with the same information as a connection that is already in global space.
To Reproduce
Steps to reproduce the behavior:
Create a new Postgres connection
Find where you can save in user/global settings
Expected behavior
A global settings checkbox.
Desktop (please complete the following information):
This is very annoying to me. I usually have several VS Code workspaces open and I'd like the same SQLTools connections to be available in all of them. After adding a new connection, I find myself having to open the settings JSON, copying the new connection from the workspace to the user settings, and deleting the workspace connection, or just opening the JSON directly and copy/pasting an existing connection instead of adding it via the dialog.
Describe the bug
On the previous Postgres driver there was an option to store the credentials in userspace vs the workspace. This option is no longer available, which causes some odd conflicts when connections are already stored there.
I would not be surprised if #567 is coming from this issue.
For instance, I can create a userspace connection with the same information as a connection that is already in global space.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
A global settings checkbox.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: