AddisDB for VS Code

AddisDB for VS Code puts your databases in the editor you already have open: every connection in the sidebar, the schema under it, and a results grid for whatever you run. It is published on the Visual Studio Marketplace and needs VS Code 1.85 or newer.

Installing it

1. In VS Code, open the Extensions view (⌘⇧X on a Mac, Ctrl+Shift+X elsewhere).
2. Search for AddisDB and install the one published by cenova-spark.
3. Or open Quick Open (⌘P / Ctrl+P) and paste the install line below.

ext install cenova-spark.addisdb

It also installs from the Marketplace web page at marketplace.visualstudio.com — search for AddisDB, or follow the link from the home page.

What happens on first run

The extension does its work through the small ‘addisdb’ command line, so the first time it activates it downloads that binary, installs it (to ~/.addisdb/bin on macOS and Linux, %LOCALAPPDATA%\AddisDB\bin on Windows), and adds it to your PATH. That needs internet access once. It keeps the binary up to date afterwards, and there is nothing for you to manage — a side effect being that ‘addisdb’ then works in any terminal, including the one inside VS Code.

If you would rather install the command line yourself, set addisdb.autoProvision to false in your settings and point addisdb.cliPath at your own binary.

What you can do with it

• Browse connections grouped by project, then schemas, tables and columns — click a table to preview its rows.
• Run the whole file, the selection, or the statement under your cursor (⌘↩ / Ctrl+Enter), with every result set returned for a multi-statement script.
• Ask what a statement does before running it, estimate what a query will cost, or count the rows it would return.
• Test SQL against a throwaway clone of the database, so the real one is never touched.
• Watch live activity and cancel or kill a running query; check and review pending migrations.
• Generate SQL with AI using your own key, under the same per-database privacy rules as the app.

Safety

Sessions open read-only. A command that needs to write asks for a writable session, and every statement is still classified by the same safety layer the desktop app uses — so a connection you saved as read-only refuses the write at the database, not just in the interface. Result sets are capped (addisdb.maxRows) so a stray SELECT * cannot hang your editor.

AI and your data

AI is bring-your-own-key and off until you set one. The AI Privacy switches you set in the desktop app apply here too — a locked column is left out of anything a model sees, and a database with AI turned off is refused by name. See “Keeping data away from AI”.