docs: adopt "instant database" terminology in hand-written prose - #176
Merged
Conversation
Rename "managed database" / "managed catalog" to "instant database" / "instant catalog" in hand-written prose (integration test docstring and comments, changelog note). Documentation only: public API symbols keep their existing "managed" naming for compatibility, and quoted server error messages are left verbatim. Generated modules and docs echo the OpenAPI spec prose and will pick up the new wording on the next regeneration from the updated spec.
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Terminology/docs change only: hand-written prose now says instant database / instant catalog instead of "managed database" / "managed catalog".
tests/integration/test_managed_tables_lifecycle.py— docstring and comments updated. Quoted server error messages are left verbatim.CHANGELOG.md— note under[Unreleased].What is intentionally NOT changed
managednaming for compatibility:ManagedTableResponse,AddManagedSchemaRequest,load_managed_table, themanagedsource type, endpoint paths, etc. are all unchanged. No code behavior changes.docs/pages will pick up the new wording automatically on the next client regeneration once the spec's description prose is updated upstream. Regenerating here ahead of that would be reverted by the next scheduled regen, so it was deliberately skipped.