Rename user-facing term "managed database" to "instant database" - #275
Conversation
Help text, README, skill docs, and code comments now say "instant database(s)". Command names, flags, and server wire-format values (e.g. the managed_load job type) and Rust identifiers keep the existing "managed" naming intentionally.
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
| "error: {e}\nSearch indexes are created on instant databases — pass a \ | ||
| instant database's catalog or id, or 'schema.table' with an active \ |
There was a problem hiding this comment.
nit: the rename leaves an article mismatch across the line continuation — the emitted message reads pass a instant database's catalog or id (not blocking).
| "error: {e}\nSearch indexes are created on instant databases — pass a \ | |
| instant database's catalog or id, or 'schema.table' with an active \ | |
| "error: {e}\nSearch indexes are created on instant databases — pass an \ | |
| instant database's catalog or id, or 'schema.table' with an active \ |
| name: hotdata | ||
| description: Use this skill when the user wants to run core hotdata CLI commands — auth, workspaces, managed databases, tables, basic SQL query, database context (context:DATAMODEL), jobs, datasources/ingests/runs (pull external data), and skill install. Activate for "run hotdata", "list workspaces", "list databases", "managed database", "load parquet", "list tables", "show table columns", "execute a query", "database context", "context:DATAMODEL", "ingest", "datasource", "ingest run", "show a run", "schedule an ingest", "import data from", "connect a data source", "connector", "pull data from postgres/mysql/an API/S3 buckets/Iceberg", or general Hotdata CLI usage. This skill bundles three specialized guides under subskills/, loaded on demand: read subskills/search/SKILL.md for full-text/vector search and retrieval indexes, subskills/analytics/SKILL.md for OLAP analytics, query history, stored results, and Chain materializations, and subskills/geospatial/SKILL.md for geospatial/GIS. | ||
| description: Use this skill when the user wants to run core hotdata CLI commands — auth, workspaces, instant databases, tables, basic SQL query, database context (context:DATAMODEL), jobs, datasources/ingests/runs (pull external data), and skill install. Activate for "run hotdata", "list workspaces", "list databases", "instant database", "load parquet", "list tables", "show table columns", "execute a query", "database context", "context:DATAMODEL", "ingest", "datasource", "ingest run", "show a run", "schedule an ingest", "import data from", "connect a data source", "connector", "pull data from postgres/mysql/an API/S3 buckets/Iceberg", or general Hotdata CLI usage. This skill bundles three specialized guides under subskills/, loaded on demand: read subskills/search/SKILL.md for full-text/vector search and retrieval indexes, subskills/analytics/SKILL.md for OLAP analytics, query history, stored results, and Chain materializations, and subskills/geospatial/SKILL.md for geospatial/GIS. | ||
| version: 0.27.1 |
There was a problem hiding this comment.
super nit: this line doubles as the skill's activation trigger list, and "managed database" was dropped rather than supplemented. Users (and existing prompts/docs) will keep saying the old term for a while, so keeping both — e.g. "instant database", "managed database" — would preserve activation on the legacy phrasing while the new term takes hold (not blocking).
There was a problem hiding this comment.
Terminology rename is consistent: markdown anchors (#instant-databases) were updated in lockstep with the headings and all cross-file links resolve, and the exclusions hold — no user-facing "managed" strings remain outside identifiers (managed_table_load_path, LoadManagedTableResponse), the managed_load wire value, historical CHANGELOG entries, and cliff.toml. Two non-blocking inline comments. Note that CI (fmt/test) was still pending when this review ran.
Codecov Report❌ Patch coverage is
📢 Thoughts on this report? Let us know! |
'Managed table' names the managed-table load endpoints and stays as-is per the cross-repo convention; only the 'managed database' -> 'instant database' product rename is in scope for this PR.
|
Pushed a fixup keeping 'managed table' wording where it names the managed-table API surface (load endpoints), per our cross-repo convention — the 'managed database' → 'instant database' rename is unchanged. |
| - `tables load` — publishes to a managed-database table (with **replace** mode) from a local parquet file (`--file`), a remote parquet URL (`--url`), a pre-staged upload (`--upload-id`), or a saved query result (`--result-id`, must belong to the target database). | ||
| - `tables remove` — drops a table from the managed database. | ||
| - `attach` — attaches a **catalog** to a managed database, so the catalog's **live** tables become visible inside that database's query scope. Defaults to the active database; target another with `--database`. `--alias` sets the SQL name the catalog answers to (defaults to the catalog's name). This is how you query an attached catalog's tables and **join across catalogs** — see [Querying across catalogs](#querying-across-catalogs-attach). | ||
| - `tables load` — publishes to an instant-database table (with **replace** mode) from a local parquet file (`--file`), a remote parquet URL (`--url`), a pre-staged upload (`--upload-id`), or a saved query result (`--result-id`, must belong to the target database). |
There was a problem hiding this comment.
super nit: the fixup restored "managed table" for the managed-table API surface in SKILL.md:147/156 and in the databases.rs load error messages, but this line (and src/commands/databases.rs:154, "Load a parquet file or a saved query result into an instant database table") still uses the new term for that same surface. If the convention is "managed table" wherever the load endpoint is named, these two read inconsistently against the errors a user actually sees (error: managed table loads require a parquet file …). (not blocking)
There was a problem hiding this comment.
Cycle 2: the fixup is a documentation-only revert of "managed table" wording on the managed-table API surface — no functional change. Verified no stray #managed-databases anchors remain and that the only surviving "managed database" strings are historical CHANGELOG entries and the cliff.toml commit-parser pattern, both intentionally excluded.
Two prior non-blocking threads are still open and unaddressed (grammar in src/commands/search.rs:275-276, dropped "managed database" activation trigger in skills/hotdata/SKILL.md:4); neither blocks merge. CI checks other than changelog had not reported at review time, so I am not claiming the build or tests pass.
1 participant
Renames the product term managed database(s) to instant database(s) everywhere it is user-facing:
databases,query,search,ingest,cli, and related modules)README.mdskills/hotdata/SKILL.md, subskills, and reference files, including section anchors)CHANGELOG.mdentry noting the terminology changeIntentionally unchanged:
databases)managed_loadjob type — a server wire-format valuemanaged_table_load_path(),LoadManagedTableResponse,JobType::ManagedLoad)CHANGELOG.mdentries andcliff.tomlcommit-parser patternscargo check --all-targetsandcargo testpass.