PartitionQueryRequest
import type { PartitionQueryRequest } from "https://googleapis.deno.dev/v1/spanner:v1.ts";The request for PartitionQuery
§Properties
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 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's an
error to execute a SQL statement with unbound parameters.
It isn't 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 query parameters. See the definition of Type for more information
about SQL types.
Additional options that affect how many partitions are created.
Required. The query request to generate partitions for. The request fails
if the query isn't root partitionable. For a query to be root
partitionable, it needs to satisfy a few conditions. For example, if the
query execution plan contains a distributed union operator, then it must be
the first operator in the plan. For more information about other
conditions, see Read data in
parallel.
The query request must not contain DML commands, such as INSERT,
UPDATE, or DELETE. Use ExecuteStreamingSql with a PartitionedDml
transaction for large, partition-friendly DML operations.
Read-only snapshot transactions are supported, read and write and single-use transactions are not.