- 3.46.0 (latest)
- 3.45.0
- 3.44.0
- 3.43.0
- 3.42.0
- 3.41.0
- 3.40.1
- 3.39.0
- 3.38.0
- 3.37.0
- 3.36.0
- 3.35.1
- 3.34.0
- 3.33.0
- 3.32.0
- 3.31.0
- 3.30.0
- 3.29.0
- 3.28.0
- 3.27.1
- 3.26.0
- 3.25.0
- 3.24.0
- 3.23.0
- 3.22.2
- 3.21.0
- 3.20.0
- 3.19.0
- 3.18.0
- 3.17.0
- 3.16.0
- 3.15.1
- 3.14.1
- 3.13.0
- 3.12.1
- 3.11.1
- 3.10.0
- 3.9.0
- 3.8.0
- 3.7.0
- 3.6.0
- 3.5.0
- 3.4.0
- 3.3.0
- 3.2.0
- 3.1.0
- 3.0.0
- 2.1.1
- 2.0.0
- 1.19.3
- 1.18.0
- 1.17.1
- 1.16.0
- 1.15.1
- 1.14.0
- 1.13.0
- 1.12.0
- 1.11.0
- 1.10.0
The request for ExecuteSql][google.spanner.v1.Spanner.ExecuteSql]
and
ExecuteStreamingSql][google.spanner.v1.Spanner.ExecuteStreamingSql]
.
The transaction to use. If none is provided, the default is a temporary read-only transaction with strong concurrency. The transaction to use. For queries, if none is provided, the default is a temporary read-only transaction with strong concurrency. Standard DML statements require a ReadWrite transaction. Single-use transactions are not supported (to avoid replay). The caller must either supply an existing transaction ID or begin a new transaction. Partitioned DML requires an existing PartitionedDml transaction ID.
The SQL string can contain parameter placeholders. A parameter
placeholder consists of '@'
followed by the parameter
name. Parameter names consist of any combination of letters,
numbers, and underscores. Parameters can appear anywhere that
a literal value is expected. The same parameter name can be
used more than once, for example: "WHERE id > @msg_id AND id
< @msg_id + 100"
It is an error to execute an SQL statement
with unbound parameters. Parameter values are specified using
params
, which is a JSON object whose keys are parameter
names, and whose values are the corresponding parameter
values.
If this request is resuming a previously interrupted SQL
statement execution, resume_token
should be copied from
the last
PartialResultSet][google.spanner.v1.PartialResultSet]
yielded
before the interruption. Doing this enables the new SQL
statement execution to resume where the last one left off. The
rest of the request parameters must exactly match the request
that yielded this token.
If present, results will be restricted to the specified partition previously created using PartitionQuery(). There must be an exact match for the values of fields common to this message and the PartitionQueryRequest message used to create this partition_token.
Classes
ParamTypesEntry
API documentation for spanner_v1.types.ExecuteSqlRequest.ParamTypesEntry
class.