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.
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)
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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 exposesGET /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 withhistoryPath.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/versionextensions) and show a "Query history" link to the returnedhistoryPath. No dependency on qbit-db-performance internals; UI API only.🤖 Generated with Claude Code