Module command 

Catalog commands that can be rechecked when committing a DDL transaction.

Statements run against the transaction’s working catalog, but the catalog can change before commit. Commands retain the original request and any output we might have sent to the client (aka. the “promise”), so commit can “assert” on that output when re-checking catalog commands against the current catalog.

Pending external work abandons the candidate. A continuation rebuilds the prefix before consuming its indexed response, so successful preparation and preparation errors are accepted only when their inputs still match.

Modules

source 🔒

source_statement 🔒

Structs

CatalogResultCommand

A catalog query whose result and notices must remain unchanged at DDL commit.

CommandExecution 🔒

Catalog writes and the outcome validation required before publishing them.

DescriptionCommand

A statement description that must remain unchanged at DDL commit.

RenameCommand

A rename or swap command.

RenameOutcome 🔒

Enums

CatalogCommand

Functions

plan_command 🔒

plan_subsource 🔒

rename_ops 🔒

Returns the rename/swap ops for the given Plan, along with the object type.