A DuckDB IDE, not a database IDE
with DuckDB in it.

Underneath

The client is DuckDB too.

DuckPlus embeds an in-memory DuckDB whose only job is to speak Quack. Every statement you run goes to the server wrapped in quack_query, so the server's own parser handles it — DDL and multi-statement scripts included — and the results come back in DuckDB's own vector format instead of passing through a generic driver.

• Schema lookups run on their own connection, so the tree never waits behind a long query
• Every query runs on a fresh clone of the connection, so a cancelled one can't block the next
• New query windows (⌘T) get their own connections to the same server
• A local file is opened by the same embedded engine, so both kinds of connection behave the same way

-- what ⌘↵ actually sends
SELECT * FROM quack_query(
  'quack:db.internal:9494',
  '<your sql>',
  token := '…'
);

Editing

Edit in the grid. Every save is one transaction.

Double-click a cell, or press ↵, and type. Edits are staged in the grid until you press ⌘S, and then they all go in one transaction. Esc first cancels the cell you're typing in, then discards everything staged.

Each UPDATE is paired with a check that its WHERE clause matches exactly one row. If it doesn't, the check raises an error inside the transaction and nothing is saved. A key column that turns out not to be unique would otherwise change several rows, and a row someone else deleted in the meantime would otherwise be skipped without telling you.

• Rows are found by the primary key, then a UNIQUE constraint, then a column you pick, then a column named id
• A plain SELECT … FROM one_table from the editor is editable too, WHERE, ORDER BY and LIMIT included
• Joins, GROUP BY, DISTINCT, CTEs and computed columns make a result read-only, because a row no longer maps to a single table row
• After a save, the query that produced the grid runs again, so your filter and ordering survive

BEGIN TRANSACTION;
SELECT CASE WHEN count(*) <> 1
  THEN error('Expected 1 row where "id" = …') END
FROM "analytics"."main"."users" WHERE "id" = '10437';
UPDATE "analytics"."main"."users"
SET "plan" = 'team', "mrr" = '49'
WHERE "id" = '10437';
COMMIT;

What ⌘S sends for two cells changed in one row. The query log records the whole transaction, so you can see exactly what was sent.