- 3.50.1 (latest)
- 3.50.0
- 3.46.0
- 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
Statement(mapping=None, *, ignore_unknown_fields=False, **kwargs)
A single DML statement.
Attributes | |
---|---|
Name | Description |
sql |
str
Required. The DML string. |
params |
Parameter names and values that bind to placeholders in the DML string. A parameter placeholder consists of the @ character
followed by the parameter name (for example,
@firstName ). Parameter names can contain 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="" +="">
It is an error to execute a SQL statement with unbound
parameters.
|
param_types |
Sequence[
It is not always possible for Cloud Spanner to infer the right SQL type from a JSON value. For example, values of type BYTES and values of type STRING both appear in
params][google.spanner.v1.ExecuteBatchDmlRequest.Statement.params]
as JSON strings.
In these cases, param_types can be used to specify the
exact SQL type for some or all of the SQL statement
parameters. See the definition of
Type][google.spanner.v1.Type] for more information about
SQL types.
|
Classes
ParamTypesEntry
ParamTypesEntry(mapping=None, *, ignore_unknown_fields=False, **kwargs)
The abstract base class for a message.
Parameters | |
---|---|
Name | Description |
kwargs |
dict
Keys and values corresponding to the fields of the message. |
mapping |
Union[dict,
A dictionary or message to be used to determine the values for this message. |
ignore_unknown_fields |
Optional(bool)
If True, do not raise errors for unknown fields. Only applied if |