Reference documentation and code samples for the Cloud Spanner V1 API class Google::Cloud::Spanner::V1::ExecuteBatchDmlRequest::Statement.
A single DML statement.
Inherits
- Object
Extended By
- Google::Protobuf::MessageExts::ClassMethods
Includes
- Google::Protobuf::MessageExts
Methods
#param_types
def param_types() -> ::Google::Protobuf::Map{::String => ::Google::Cloud::Spanner::V1::Type}
-
(::Google::Protobuf::Map{::String => ::Google::Cloud::Spanner::V1::Type}) — 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 typeSTRING
both appear in 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 for more information about SQL types.
#param_types=
def param_types=(value) -> ::Google::Protobuf::Map{::String => ::Google::Cloud::Spanner::V1::Type}
-
value (::Google::Protobuf::Map{::String => ::Google::Cloud::Spanner::V1::Type}) — 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 typeSTRING
both appear in 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 for more information about SQL types.
-
(::Google::Protobuf::Map{::String => ::Google::Cloud::Spanner::V1::Type}) — 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 typeSTRING
both appear in 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 for more information about SQL types.
#params
def params() -> ::Google::Protobuf::Struct
-
(::Google::Protobuf::Struct) — 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 + 100"
It is an error to execute a SQL statement with unbound parameters.
#params=
def params=(value) -> ::Google::Protobuf::Struct
-
value (::Google::Protobuf::Struct) — 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 + 100"
It is an error to execute a SQL statement with unbound parameters.
-
(::Google::Protobuf::Struct) — 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 + 100"
It is an error to execute a SQL statement with unbound parameters.
#sql
def sql() -> ::String
- (::String) — Required. The DML string.
#sql=
def sql=(value) -> ::String
- value (::String) — Required. The DML string.
- (::String) — Required. The DML string.