class Google::Apis::SpannerV1::UpdateDatabaseDdlRequest
details.
the Operations API to monitor progress. See the operation_id field for more
cancelled. Each batch of statements is assigned a name which can be used with
If a statement fails, all subsequent statements in the batch are automatically
problem like a ‘NULL` value in a column to which `NOT NULL` would be added).
applied first and it conflicts in some way, or if there is some data-related
upon later execution (e.g., if a statement from another batch of statements is
name tables that exist, etc.) before enqueueing them, but they may still fail
The server checks that the statements are executable (syntactically valid,
all at once, to the database schema at some point (or points) in the future.
Enqueues the given DDL statements to be applied, in order but not necessarily
def initialize(**args)
def initialize(**args) update!(**args) end
def update!(**args)
def update!(**args) @operation_id = args[:operation_id] if args.key?(:operation_id) @statements = args[:statements] if args.key?(:statements) end