pub struct ResultSet {
pub metadata: Option<ResultSetMetadata>,
pub precommit_token: Option<MultiplexedSessionPrecommitToken>,
pub rows: Option<Vec<Vec<Value>>>,
pub stats: Option<ResultSetStats>,
}Expand description
Results from Read or ExecuteSql.
§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 (response)
- instances databases sessions read projects (response)
Fields§
§metadata: Option<ResultSetMetadata>Metadata about the result set, such as row type information.
precommit_token: Option<MultiplexedSessionPrecommitToken>Optional. A precommit token is included if the read-write transaction is on a multiplexed session. Pass the precommit token with the highest sequence number from this transaction attempt to the Commit request for this transaction.
rows: Option<Vec<Vec<Value>>>Each element in rows is a row whose format is defined by metadata.row_type. The ith element in each row matches the ith field in metadata.row_type. Elements are encoded based on type as described here.
stats: Option<ResultSetStats>Query plan and execution statistics for the SQL statement that produced this result set. These can be requested by setting ExecuteSqlRequest.query_mode. DML statements always produce stats containing the number of rows modified, unless executed using the ExecuteSqlRequest.QueryMode.PLAN ExecuteSqlRequest.query_mode. Other fields might or might not be populated, based on the ExecuteSqlRequest.query_mode.