Ruben Fiszel 55451db009 fix(datatable): self-teaching error for unresolved datatable:// references (#9941) ...

`ATTACH 'datatable://main'` (or any datatable schema/executor path) failed
with a bare "datatable main not found", giving the user no way forward — the
datatable substrate has no auto-provisioning like a DuckLake catalog, so the
fix is always to create one in workspace settings, but nothing said so.

`get_datatable_resource_from_db_unchecked` now returns a NotFound error that
lists the workspace's configured data tables (to catch typos) and points at
the "Data tables" settings tab, noting `main` is the default name used by
`datatable://main`. The message bubbles up wherever the resolver is called
(pipeline ATTACH, schema fetch, postgres executor, agent HTTP endpoint).

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>

2026-07-05 23:08:08 +02:00

..

examples

fix: enrich OTEL log records with per-request LogContext (#8812)

2026-04-13 21:50:50 +00:00

src

fix(datatable): self-teaching error for unresolved datatable:// references (#9941)

2026-07-05 23:08:08 +02:00

tests

feat: support workspace forks on cloud using parent workspace limits (#9864)

2026-07-02 23:59:02 +02:00

Cargo.toml

feat: Db-backed user drafts (#9351)

2026-06-15 10:23:16 +02:00