Skip to content

docs: duckdb vscode warning #4746

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
benfdking merged 2 commits into from
Jun 16, 2025
Merged

docs: duckdb vscode warning #4746

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
0c1e23f
docs: duckdb vscode warning
benfdking Jun 16, 2025
04ba05a
Update docs/guides/vscode.md
benfdking Jun 16, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions docs/guides/vscode.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -139,6 +139,16 @@ The SQLMesh VSCode extension provides the following commands in the VSCode comma

## Troubleshooting

### DuckDB concurrent access

If your SQLMesh project uses DuckDB to store its state, you will likely encounter problems.

SQLMesh can create multiple connections to the state database, but DuckDB's local database file does not support concurrent access.

Because the VSCode extension establishes a long-running process connected to the database, access conflicts are more likely than with standard SQLMesh usage from the CLI.

Therefore, we do not recommend using DuckDB as a state store with the VSCode extension.

### Python environment woes

The most common problem is the extension not using the correct Python interpreter.
Expand Down