qbit-sql-workbench

62 Commits 40 Branches 9 Tags

3 Commits

Include renames

Author	SHA1	Message	Date
james.maesandClaude Opus 5.5	7c2d0610a5	fix(ddl): index result_snapshot.notebook_id and execution.notebook_id The foreign key sql_workbench_result_snapshot.notebook_id had no index. NotebookService lists a notebook's snapshots by it, the notebook delete cascade and the child record lock use it, and the notebook page's Runs list joins executions on notebook_id. The reference DDL and the H2 test schema add both indexes. The Postgres integration test now fails if any sql_workbench_ foreign-key column lacks a leading index. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-14 15:28:18 -05:00
james.maesandClaude Opus 5.5	ddd85ebe0d	feat(#3 ): expose workbench data as standard QQQ tables secured by record locks Notebooks, cells, versions, pinned results, shares and the execution audit are now ordinary QQQ tables in the SQL Workbench app (nav children, record views with child lists, edit, export, audits, developer mode) instead of hidden admin-only tables. - Record security locks (core-enforced, so every entry point): owner OR share audience for notebooks and their children (through joins), the audit by user; admins hold sqlWorkbenchAllAccess. Key types sqlWorkbenchUser / sqlWorkbenchAudience, applied to sessions by SqlWorkbenchSecurity.applyToSession (no keys without workbench access). - New sqlWorkbenchNotebookShare (USER / GROUP / ALL); publishing writes an ALL share and visibility follows the shares. - Per-table read/insert/edit/delete permissions, listed per role by the config (user / share / admin). - Table customizers hold the notebook invariants for the notebook UI and the tables alike: owner from the session, cell validation and order, one version per change, share keys, append-only versions and audit (admins included), pinned results only from pinning, cascades. - NotebookService and history run as the caller through the same actions; explicit owner/share checks stay as defense in depth. - Record actions: Share Notebook, Duplicate Notebook, Restore Version. - DDL: share table plus an idempotent backfill of library shares. - Tests: TableSecurityMatrixTest (role x table x action over the v1 table API, core actions, export, PVS, record actions, notebook endpoints) and a PostgreSQL lock test. Docs: README, DESIGN, CHANGELOG. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-12 06:08:10 -05:00
james.maesandClaude Opus 5.5	b8d33460bf	feat: SQL Workbench qbit 1.0 backend QQQ 4.1 QBit (com.kingsrook.qbits:sql-workbench) for a super-user SQL notebook over any RDBMS backend of the instance: - Dialect-aware scanner, statement splitter/classifier (READ, EXPLAIN_ANALYZE, WRITE, DDL, FORBIDDEN) and :named parameter binding. - Execution engine: read-only sessions in a database READ ONLY transaction (Postgres, MySQL, SQLite query_only; classifier on H2), gated write mode (rolled-back dry run, single-use confirm token, row guard, hard cap, drift check), statement timeouts, row/byte caps, cancellation, per-user concurrency, clean connection return, and a fail-closed execution audit (audit updates deferred until the session connection is released). - Dedicated read-only/write credentials per backend; backend read-only replica support. - EXPLAIN / EXPLAIN ANALYZE (always rolled back) normalized to a plan tree; schema introspection with QQQ table/field -> SQL name mapping. - Notebooks (personal/shared), cells, versions with retention, result snapshots. - REST routes under /qqq/v1/sql-workbench (Javalin 7, JSON-only bodies), CSV/XLSX/JSON export. - Tables, notebook PVS, SQL_WORKBENCH widget and sqlWorkbench app; no processes. PostgreSQL DDL in docs/ddl/postgres.sql. - Tests: 83 unit (H2, SQLite, HTTP) + 6 Testcontainers Postgres integration tests; JaCoCo 94% instructions. - CircleCI qqq-orb 0.6.8 config, Maven wrapper, CLAUDE.md/AGENTS.md, CHANGELOG. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-11 09:47:40 -05:00

Author

SHA1

Message

Date

james.maesandClaude Opus 5.5

7c2d0610a5

fix(ddl): index result_snapshot.notebook_id and execution.notebook_id

The foreign key sql_workbench_result_snapshot.notebook_id had no index.
NotebookService lists a notebook's snapshots by it, the notebook delete
cascade and the child record lock use it, and the notebook page's Runs
list joins executions on notebook_id. The reference DDL and the H2 test
schema add both indexes. The Postgres integration test now fails if any
sql_workbench_ foreign-key column lacks a leading index.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-14 15:28:18 -05:00

james.maesandClaude Opus 5.5

ddd85ebe0d

feat(#3 ): expose workbench data as standard QQQ tables secured by record locks

Notebooks, cells, versions, pinned results, shares and the execution
audit are now ordinary QQQ tables in the SQL Workbench app (nav children,
record views with child lists, edit, export, audits, developer mode)
instead of hidden admin-only tables.

- Record security locks (core-enforced, so every entry point): owner OR
  share audience for notebooks and their children (through joins), the
  audit by user; admins hold sqlWorkbenchAllAccess. Key types
  sqlWorkbenchUser / sqlWorkbenchAudience, applied to sessions by
  SqlWorkbenchSecurity.applyToSession (no keys without workbench access).
- New sqlWorkbenchNotebookShare (USER / GROUP / ALL); publishing writes an
  ALL share and visibility follows the shares.
- Per-table read/insert/edit/delete permissions, listed per role by the
  config (user / share / admin).
- Table customizers hold the notebook invariants for the notebook UI and
  the tables alike: owner from the session, cell validation and order,
  one version per change, share keys, append-only versions and audit
  (admins included), pinned results only from pinning, cascades.
- NotebookService and history run as the caller through the same actions;
  explicit owner/share checks stay as defense in depth.
- Record actions: Share Notebook, Duplicate Notebook, Restore Version.
- DDL: share table plus an idempotent backfill of library shares.
- Tests: TableSecurityMatrixTest (role x table x action over the v1 table
  API, core actions, export, PVS, record actions, notebook endpoints) and
  a PostgreSQL lock test. Docs: README, DESIGN, CHANGELOG.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-12 06:08:10 -05:00

james.maesandClaude Opus 5.5

b8d33460bf

feat: SQL Workbench qbit 1.0 backend

QQQ 4.1 QBit (com.kingsrook.qbits:sql-workbench) for a super-user SQL
notebook over any RDBMS backend of the instance:

- Dialect-aware scanner, statement splitter/classifier (READ,
  EXPLAIN_ANALYZE, WRITE, DDL, FORBIDDEN) and :named parameter binding.
- Execution engine: read-only sessions in a database READ ONLY
  transaction (Postgres, MySQL, SQLite query_only; classifier on H2),
  gated write mode (rolled-back dry run, single-use confirm token,
  row guard, hard cap, drift check), statement timeouts, row/byte caps,
  cancellation, per-user concurrency, clean connection return, and a
  fail-closed execution audit (audit updates deferred until the
  session connection is released).
- Dedicated read-only/write credentials per backend; backend read-only
  replica support.
- EXPLAIN / EXPLAIN ANALYZE (always rolled back) normalized to a plan
  tree; schema introspection with QQQ table/field -> SQL name mapping.
- Notebooks (personal/shared), cells, versions with retention, result
  snapshots.
- REST routes under /qqq/v1/sql-workbench (Javalin 7, JSON-only
  bodies), CSV/XLSX/JSON export.
- Tables, notebook PVS, SQL_WORKBENCH widget and sqlWorkbench app; no
  processes. PostgreSQL DDL in docs/ddl/postgres.sql.
- Tests: 83 unit (H2, SQLite, HTTP) + 6 Testcontainers Postgres
  integration tests; JaCoCo 94% instructions.
- CircleCI qqq-orb 0.6.8 config, Maven wrapper, CLAUDE.md/AGENTS.md,
  CHANGELOG.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-11 09:47:40 -05:00