microsoft / microsoft/vscode-pgsql
Go to Definition is not working
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 395
- Forks
- 33
- Avg merge
- 1h 46m
- Merged PRs (30d)
- 3
Description
Describe the bug
The context menu options "Go to Definition" and "Peek Definition" always returns "No Definition found for '...'"
To Reproduce
Steps to reproduce the behavior:
- Go to an .sql file or opened with "Script as create" from the siebar with pgsql code inside
- Right Click on a function call inside and select "Go to Definition"
- See error
Expected behavior
I Expect that the code that a file will be opened. Same like I would click "Script as create" on the function
VS Code version
Version: 1.107.1 (system setup)
Commit: 994fd12f8d3a5aa16f17d42c041e5809167e845a
Date: 2025-12-17T14:15:14.850Z (2 days ago)
Electron: 39.2.3
ElectronBuildId: 12895514
Chromium: 142.0.7444.175
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Windows_NT x64 10.0.22631
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
Start by reproducing the failure in a .sql file or a script opened with “Script as create,” using a PostgreSQL function call. Compare “Go to Definition” and “Peek Definition” with the existing “Script as create” behavior; done means the function’s code opens instead of showing “No Definition found.”
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgresql, sql, vscode
- Domain
- databases, developer-experience
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100