Module mz_adapter::catalog::storage
source · Re-exports
pub use stash::AUDIT_LOG_COLLECTION;
pub use stash::CLUSTER_COLLECTION;
pub use stash::CLUSTER_INTROSPECTION_SOURCE_INDEX_COLLECTION;
pub use stash::CLUSTER_REPLICA_COLLECTION;
pub use stash::COMMENTS_COLLECTION;
pub use stash::CONFIG_COLLECTION;
pub use stash::DATABASES_COLLECTION;
pub use stash::DEFAULT_PRIVILEGES_COLLECTION;
pub use stash::ID_ALLOCATOR_COLLECTION;
pub use stash::ITEM_COLLECTION;
pub use stash::ROLES_COLLECTION;
pub use stash::SCHEMAS_COLLECTION;
pub use stash::SETTING_COLLECTION;
pub use stash::STORAGE_USAGE_COLLECTION;
pub use stash::SYSTEM_CONFIGURATION_COLLECTION;
pub use stash::SYSTEM_GID_MAPPING_COLLECTION;
pub use stash::SYSTEM_PRIVILEGES_COLLECTION;
pub use stash::TIMESTAMP_COLLECTION;
Modules
Structs
- A
Connection
represent an open connection to the stash. It exposes optimized methods for executing a single operation against the stash. If the consumer needs to execute multiple operations atomically, then they should start a transaction viaConnection::transaction
. - Functions can share the same name as any other catalog item type within a given schema. For example, a function can have the same name as a type, e.g. ‘date’. As such, system objects are keyed in the catalog storage by the tuple (schema_name, object_type, object_name), which is guaranteed to be unique.
- A
Transaction
batches multipleConnection
operations together and commits them atomically.