microsoft / microsoft/vscode-pgsql
SQL queries files management
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 395
- Forks
- 33
- Avg merge
- 1h 46m
- Merged PRs (30d)
- 3
Description
I would like to be able to manage my sql queries files from commands and UIs actions.
- I'd like to be able to link files to a database, table, etc. These files are saved either locally or user-scoped (so I can find them from another computer using the user account)
- Commands :
- "Open/create linked file" -> Choose connection profile -> Choose database -> List of linked files and "create new" option.
- "Delete linked file" -> Choose connection profile -> Choose database -> Choose linked file -> confirmation.
- "See linked files in file explorer" -> Opens file explorer where script files are located.
- "Open default file". Allow me to mark a single file per database/table/db element as "default". The command asks the user to select connection profile and database. If the file doesn't exists, creates it.
- Right click on a database/table/db element shows these commands without having to choose the connection profile and db element.
- When opening a linked file, it shows the connection, database[,table/db element, ...] and file within the breadcrumbs.
- The breadcrumbs allows to switch file, database and connection profile.
- Commands :
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
Begin by tracing the existing command and UI entry points for connection profiles, databases, and SQL files, then map the requested linked-file and breadcrumb flows. Done means users can create, open, delete, browse, and select default files for database elements from commands and contextual UI actions, with the requested connection and database context visible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, sql, vscode
- Domain
- cli, database, desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100