Link from SQL Workbench to a query's history in Database Performance #30

Open
opened 2026-10-15 23:16:35 +00:00 by KofTwentyTwo · 0 comments
KofTwentyTwo commented 2026-10-15 23:16:35 +00:00 (Migrated from github.com)

Owner decision (2026-10-15, qbit-db-performance D1): SQL Workbench and Database Performance link both ways.

Done: Database Performance links each statement to the Workbench runner (sqlWorkbenchRunnerPath?sql=EXPLAIN ...), and exposes GET /qqq/v1/qbit/db-performance/statements/lookup?backend=&sql= which normalizes and fingerprints SQL the same way pg_stat_statements does and returns matching statements with historyPath.

To do (here and in qqq-frontend-next): after a cell runs, call the lookup operation (only when the extension is registered, via GET /qqq/v1/version extensions) and show a "Query history" link to the returned historyPath. No dependency on qbit-db-performance internals; UI API only.

🤖 Generated with Claude Code

Owner decision (2026-10-15, qbit-db-performance D1): SQL Workbench and Database Performance link both ways. Done: Database Performance links each statement to the Workbench runner (`sqlWorkbenchRunnerPath?sql=EXPLAIN ...`), and exposes `GET /qqq/v1/qbit/db-performance/statements/lookup?backend=&sql=` which normalizes and fingerprints SQL the same way pg_stat_statements does and returns matching statements with `historyPath`. To do (here and in qqq-frontend-next): after a cell runs, call the lookup operation (only when the extension is registered, via `GET /qqq/v1/version` extensions) and show a "Query history" link to the returned `historyPath`. No dependency on qbit-db-performance internals; UI API only. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: QRun-IO/qbit-sql-workbench#30