Expand description
Data definition language (DDL).
This module houses the handlers for statements that modify the catalog, like
ALTER, CREATE, and DROP.
Modules§
- Data definition language (DDL) utilities for CONNECTION objects.
Structs§
- Creating this by hand instead of using generate_extracted_config! macro because the macro doesn’t support parameterized enums. See https://github.com/MaterializeInc/database-issues/issues/6698
Enums§
Constants§
Functions§
- Given a relation desc and a column list, checks that:
- Returns
trueif the cluster has any storage object. Returnfalseif the cluster has no objects. - Does the dependency
depprevent a drop of a non-cascade query? - Returns an error if the given cluster is a managed cluster
- Extract the key envelope, if it is requested
- Gets the key envelope for a given key encoding when no name for the key has been requested by the user.
- Convert a
ClusterScheduleOptionValueinto aClusterSchedule. - Convert a
CreateClusterStatementinto aPlan. - Returns the
CatalogItemIdof the item we should drop, if it exists. - This function will plan a sink as if it does not exist in the catalog. This is so the planning logic is reused by both CREATE SINK and ALTER SINK planning. It is the responsibility of the callers (plan_create_sink and plan_alter_sink) to check for name collisions if this is important.
- Plans the RelationDesc for a source export (subsource or table) that has a defined list of columns and constraints.
- Determine the cluster ID to use for this item.
- Convert a
ClusterScheduleinto aClusterScheduleOptionValue. - Convert a
CreateClusterPlaninto aCreateClusterStatement.