microsoft / microsoft/vscode-pgsql
[Feature Request] Explicit Connection Management Actions (Connect / Reconnect / Disconnect)
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 395
- Forks
- 33
- Avg merge
- 1h 46m
- Merged PRs (30d)
- 3
Description
Feature Description
I’d like to request more explicit connection management actions in the vscode-pgsql extension for Visual Studio Code, including dedicated options for Connect, Reconnect (Invalidate), and Disconnect.
Proposed Capabilities
- Explicit Connect action to manually establish a database connection.
- Reconnect / Invalidate Connection option to:
- Refresh stale or expired connections
- Clear cached sessions or credentials
- Disconnect action to explicitly close an active connection.
- Clear visual indicators for connection state:
- Connected
- Disconnected
- Stale / invalid
- Access to these actions from:
- Connection context menu
- Toolbar or Command Palette
- Optional keyboard shortcuts for faster workflows.
Problem & Motivation
Currently, connection state handling in vscode-pgsql can feel implicit or unclear. When credentials expire, VPNs change, or sessions become stale, there is no clear way to explicitly invalidate and reconnect a connection.
This can lead to:
- Confusing connection errors
- Queries failing due to stale sessions
- Recreating connections unnecessarily
Use Case
- Switching between local, staging, and production environments
- Working with VPNs or unstable networks
- Refreshing credentials or tokens
- Managing multiple active connections safely
Request
Please consider adding explicit Connect, Reconnect (Invalidate), and Disconnect actions to improve clarity, reliability, and overall user experience in vscode-pgsql.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source files, tests, or entry points are identified in the issue. Start by locating the extension's existing connection-state handling and commands, then define how Connect, Reconnect/Invalidate, and Disconnect should behave across the connection menu and Command Palette. Done should include explicit actions and clear connected, disconnected, and stale states.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, vscode
- Domain
- databases, developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100