Struct ExecuteSqlRequest

pub struct ExecuteSqlRequest {
    pub data_boost_enabled: Option<bool>,
    pub directed_read_options: Option<DirectedReadOptions>,
    pub param_types: Option<HashMap<String, Type>>,
    pub params: Option<HashMap<String, Value>>,
    pub partition_token: Option<Vec<u8>>,
    pub query_mode: Option<String>,
    pub query_options: Option<QueryOptions>,
    pub request_options: Option<RequestOptions>,
    pub resume_token: Option<Vec<u8>>,
    pub seqno: Option<i64>,
    pub sql: Option<String>,
    pub transaction: Option<TransactionSelector>,
}

The request for ExecuteSql and ExecuteStreamingSql.

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 sql projects (request)
• instances databases sessions execute streaming sql projects (request)

Fields

data_boost_enabled: Option<bool>

If this is for a partitioned query and this field is set to true, the request is executed with Spanner Data Boost independent compute resources. If the field is set to true but the request does not set partition_token, the API returns an INVALID_ARGUMENT error.

directed_read_options: Option<DirectedReadOptions>

Directed read options for this request.

param_types: Option<HashMap<String, 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 type STRING 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: Option<HashMap<String, Value>>

Parameter names and values that bind to placeholders in the SQL string. A parameter placeholder consists of the @ character followed by the parameter name (for example, @firstName). Parameter names must conform to the naming requirements of identifiers as specified at https://cloud.google.com/spanner/docs/lexical#identifiers. 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.

partition_token: Option<Vec<u8>>

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.

query_mode: Option<String>

Used to control the amount of debugging information returned in ResultSetStats. If partition_token is set, query_mode can only be set to QueryMode.NORMAL.

query_options: Option<QueryOptions>

Query optimizer configuration to use for the given query.

request_options: Option<RequestOptions>

Common options for this request.

resume_token: Option<Vec<u8>>

If this request is resuming a previously interrupted SQL statement execution, resume_token should be copied from the last 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.

seqno: Option<i64>

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. Required for DML statements. Ignored for queries.

sql: Option<String>

Required. The SQL string.

transaction: Option<TransactionSelector>

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 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. Partitioned DML requires an existing Partitioned DML transaction ID.

Trait Implementations

impl Clone for ExecuteSqlRequest

fn clone(&self) -> ExecuteSqlRequest

Returns a duplicate of the value.

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

Performs copy-assignment from source.

impl Debug for ExecuteSqlRequest

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

Formats the value using the given formatter.

impl Default for ExecuteSqlRequest

fn default() -> ExecuteSqlRequest

Returns the “default value” for a type.

impl<'de> Deserialize<'de> for ExecuteSqlRequest

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

where __D: Deserializer<'de>,

Deserialize this value from the given Serde deserializer.

impl Serialize for ExecuteSqlRequest

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 ExecuteSqlRequest