- 1.104.0 (latest)
- 1.103.0
- 1.102.0
- 1.101.0
- 1.100.0
- 1.98.0
- 1.97.0
- 1.96.0
- 1.95.0
- 1.94.0
- 1.93.1
- 1.92.1
- 1.91.0
- 1.90.0
- 1.89.0
- 1.88.0
- 1.87.0
- 1.86.0
- 1.85.0
- 1.84.0
- 1.83.0
- 1.82.0
- 1.81.0
- 1.80.0
- 1.79.0
- 1.78.0
- 1.77.0
- 1.76.1
- 1.68.0
- 1.67.0
- 1.66.0
- 1.65.0
- 1.64.0
- 1.63.2
- 1.62.1
- 1.61.0
- 1.60.0
- 1.59.0
- 1.58.4
- 1.57.0
- 1.56.0
- 1.55.0
- 1.54.2
Reference documentation and code samples for the Cloud Spanner V1 Client class ExecuteBatchDmlRequest.
The request for ExecuteBatchDml .
Generated from protobuf message google.spanner.v1.ExecuteBatchDmlRequest
Methods
__construct
Constructor.
data
array
Optional. Data for populating the Message object.
↳ session
string
Required. The session in which the DML statements should be performed.
↳ transaction
Google\Cloud\Spanner\V1\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.
↳ statements
array< Google\Cloud\Spanner\V1\ExecuteBatchDmlRequest\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.
↳ seqno
int|string
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 will succeed. 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 may be aborted. Replays of previously handled requests will yield the same response as the first execution.
↳ request_options
getSession
Required. The session in which the DML statements should be performed.
string
setSession
Required. The session in which the DML statements should be performed.
var
string
$this
getTransaction
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.
hasTransaction
clearTransaction
setTransaction
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.
$this
getStatements
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.
setStatements
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.
$this
getSeqno
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 will succeed.
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 may be aborted. Replays of previously handled requests will yield the same response as the first execution.
int|string
setSeqno
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 will succeed.
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 may be aborted. Replays of previously handled requests will yield the same response as the first execution.
var
int|string
$this
getRequestOptions
Common options for this request.
hasRequestOptions
clearRequestOptions
setRequestOptions
Common options for this request.
$this
