Feature Request: Global Queries/Global Query Folder
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 485
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
I very often find myself saving queries that I might want to run globally across all of the RDS servers I connect to-- queries to check table index usage patterns, query to see all triggers, query to see non-idle processes, query to see all processes, etc. But also queries specific to our particular database, which are relevant for all clients and could be useful for debugging.
I have them saved in the "Queries" panel so I don't have to copy/paste them every time, but they only exist on whatever database connection I originally used them on.
So then I have to remember to copy/paste them over to the various other connections. And if I make changes, I then have to also remember to copy again. I also run into the issue of forgetting which connection I used that really awesome query on 3 months ago-- and then have to go through them all to find it (maybe not an issue if you only connect to 1-2 different servers, but I'm looking at 12-13 right now).
It would be awesome to have a designated "Global Queries" folder into which I could place all of these saved queries. And then that folder could be available across all database connections. Or even better, allow a query folder to be specified as a "global" folder, so you could have multiple if you wanted.
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 files or tests are named. Start by locating the query-saving and folder-scoping entry points, then determine how saved queries are associated with connections. Done should include a global folder or global folder setting whose queries are available across database connections and remain synchronized after edits.
Written by the indexing model from the issue text.
Assessment
- Domain
- database, desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100