#[non_exhaustive]pub struct BatchStatementRequest {
pub statement: String,
pub parameters: Option<Vec<AttributeValue>>,
pub consistent_read: Option<bool>,
pub return_values_on_condition_check_failure: Option<String>,
}Expand description
One member of a batch.
#[non_exhaustive] because DynamoDB grows this shape and has already grown
it twice here: ConsistentRead and ReturnValuesOnConditionCheckFailure
both arrived after the type was first written. The attribute means the next
one costs consumers nothing. Construct one from Default and assign, or
deserialise it. The enclosing BatchExecuteStatementRequest is deliberately
not marked: it carries Statements and ReturnConsumedCapacity, which is
the whole of DynamoDB’s shape.
Fields (Non-exhaustive)§
This struct is marked as non-exhaustive
Struct { .. } syntax; cannot be matched against without a wildcard ..; and struct update syntax will not work.statement: String§parameters: Option<Vec<AttributeValue>>§consistent_read: Option<bool>Per member, not per batch. Does not change which rows come back, because
every read against SQLite is already strongly consistent, but it does
change the rate the read is charged at: a keyed batch SELECT costs 0.5
without it and 1 with it, and a batch mixing the two sums both rates.
Captured eu-west-2 2026-08-15.
return_values_on_condition_check_failure: Option<String>Accepted and inert, which is what DynamoDB does with it. A batch member
whose condition fails returns the same response whether this is
ALL_OLD, NONE, or absent, and never carries the item: measured
against a TransactWriteItems ConditionCheck in the same round, which
does return it. The field is deserialised so a client setting it meets a
field dynoxide knows rather than one it drops.