Skip to content

docs: adopt "instant database" terminology in hand-written prose #176

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
eddietejeda merged 1 commit into from
Aug 25, 2026
+9 −4
Merged

docs: adopt "instant database" terminology in hand-written prose #176

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,11 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

### Changed

- docs: adopt "instant database" / "instant catalog" terminology in hand-written
prose. Documentation only — all public API symbols (`ManagedTableResponse`,
`load_managed_table`, the `managed` source type, etc.) are unchanged for
compatibility. Generated docstrings pick up the new wording on the next client
regeneration from the updated OpenAPI spec.
- feat(query): add dialect parameter to query request

## [0.10.0] - 2026-08-18
Expand Down
8 changes: 4 additions & 4 deletions tests/integration/test_managed_tables_lifecycle.py
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,18 +1,18 @@
"""Scenario: managed_tables_lifecycle.

The heaviest scenario — it ties databases, uploads, and managed tables together
against a fresh scratch database (whose default catalog is a managed catalog):
against a fresh scratch database (whose default catalog is an instant catalog):

1. declare a schema and a table on the database's default catalog connection,
2. upload a small parquet file,
3. load it into the table (load_managed_table) and verify the load response,
4. delete the managed table.

Notes on managed-catalog semantics (all confirmed against prod). A managed
Notes on instant-catalog semantics (all confirmed against prod). An instant
catalog rejects the maintenance ops that apply to external catalogs, so this
scenario deliberately omits them:

* No `refresh` step — rejected with 400 on a managed catalog ("use the loads
* No `refresh` step — rejected with 400 on an instant catalog ("use the loads
endpoint to update its data"); `load_managed_table` is itself the load.
* No `purge_table_cache` step — rejected with 400 ("purge not supported for
managed catalogs").
Expand Down Expand Up @@ -55,7 +55,7 @@ def test_managed_tables_lifecycle(
uploads_api: UploadsApi,
scratch_database: str,
) -> None:
# The database's auto-provisioned default catalog is a managed catalog,
# The database's auto-provisioned default catalog is an instant catalog,
# addressed through its default_connection_id.
connection_id = databases_api.get_database(scratch_database).default_connection_id
schema_name = "sdkci_mt"
Expand Down