Skip to content

Commit 04ba05a

Browse files
benfdkingtreysp
andauthored
Update docs/guides/vscode.md
Co-authored-by: Trey Spiller <1831878+treysp@users.noreply.github.com>
1 parent 0c1e23f commit 04ba05a

1 file changed

Lines changed: 7 additions & 1 deletion

File tree

docs/guides/vscode.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -141,7 +141,13 @@ The SQLMesh VSCode extension provides the following commands in the VSCode comma
141141

142142
### DuckDB concurrent access
143143

144-
If you are using DuckDB as your state store, you are likely to encounter problems with concurrent access to the DuckDB database file. The DuckDB database file is a single file on disk, and it does not support concurrent access from multiple processes. The extension uses a long-running process to provide its features. This long-running requires access, and so there is a risk of database locks. We don't recommend using DuckDB as a state store with the VSCode extension for this reason.
144+
If your SQLMesh project uses DuckDB to store its state, you will likely encounter problems.
145+
146+
SQLMesh can create multiple connections to the state database, but DuckDB's local database file does not support concurrent access.
147+
148+
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.
149+
150+
Therefore, we do not recommend using DuckDB as a state store with the VSCode extension.
145151

146152
### Python environment woes
147153

0 commit comments

Comments
 (0)