Struct ExecuteBatchDmlRequest 

pub struct ExecuteBatchDmlRequest {
    pub last_statements: Option<bool>,
    pub request_options: Option<RequestOptions>,
    pub seqno: Option<i64>,
    pub statements: Option<Vec<Statement>>,
    pub transaction: Option<TransactionSelector>,
}

The request for ExecuteBatchDml.

Activities

This type is used in activities, which are methods you may call on this type or where this type is involved in. The list links the activity name, along with information about where it is used (one of request and response).

• instances databases sessions execute batch dml projects (request)

Fields

last_statements: Option<bool>

Optional. If set to true, this request marks the end of the transaction. After these statements execute, you must commit or abort the transaction. Attempts to execute any other requests against this transaction (including reads and queries) are rejected. Setting this option might cause some error reporting to be deferred until commit time (for example, validation of unique constraints). Given this, successful execution of statements shouldn’t be assumed until a subsequent Commit call completes successfully.

request_options: Option<RequestOptions>

Common options for this request.

seqno: Option<i64>

Required. A per-transaction sequence number used to identify this request. This field makes each request idempotent such that if the request is received multiple times, at most one succeeds. The sequence number must be monotonically increasing within the transaction. If a request arrives for the first time with an out-of-order sequence number, the transaction might be aborted. Replays of previously handled requests yield the same response as the first execution.

statements: Option<Vec<Statement>>

Required. The list of statements to execute in this batch. Statements are executed serially, such that the effects of statement i are visible to statement i+1. Each statement must be a DML statement. Execution stops at the first failed statement; the remaining statements are not executed. Callers must provide at least one statement.

transaction: Option<TransactionSelector>

Required. The transaction to use. Must be a read-write transaction. To protect against replays, single-use transactions are not supported. The caller must either supply an existing transaction ID or begin a new transaction.

Trait Implementations

impl Clone for ExecuteBatchDmlRequest

fn clone(&self) -> ExecuteBatchDmlRequest

Returns a duplicate of the value.

fn clone_from(&mut self, source: &Self)

Performs copy-assignment from source.

impl Debug for ExecuteBatchDmlRequest

fn fmt(&self, f: &mut Formatter<'_>) -> Result

Formats the value using the given formatter.

impl Default for ExecuteBatchDmlRequest

fn default() -> ExecuteBatchDmlRequest

Returns the “default value” for a type.

impl<'de> Deserialize<'de> for ExecuteBatchDmlRequest

fn deserialize<__D>(__deserializer: __D) -> Result<Self, __D::Error>

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl Serialize for ExecuteBatchDmlRequest

fn serialize<__S>(&self, __serializer: __S) -> Result<__S::Ok, __S::Error>

where __S: Serializer,

Serialize this value into the given Serde serializer.

impl RequestValue for ExecuteBatchDmlRequest