Transaction(mapping=None, *, ignore_unknown_fields=False, **kwargs)A transaction.
Attributes |
|
|---|---|
| Name | Description |
id |
bytes
id may be used to identify the transaction in subsequent
Read][google.spanner.v1.Spanner.Read],
ExecuteSql][google.spanner.v1.Spanner.ExecuteSql],
Commit][google.spanner.v1.Spanner.Commit], or
Rollback][google.spanner.v1.Spanner.Rollback] calls.
Single-use read-only transactions do not have IDs, because
single-use transactions do not support multiple requests.
|
read_timestamp |
google.protobuf.timestamp_pb2.Timestamp
For snapshot read-only transactions, the read timestamp chosen for the transaction. Not returned by default: see TransactionOptions.ReadOnly.return_read_timestamp][google.spanner.v1.TransactionOptions.ReadOnly.return_read_timestamp].
A timestamp in RFC3339 UTC "Zulu" format, accurate to
nanoseconds. Example: "2014-10-02T15:01:23.045123456Z".
|
precommit_token |
google.cloud.spanner_v1.types.MultiplexedSessionPrecommitToken
A precommit token is included in the response of a BeginTransaction request if the read-write transaction is on a multiplexed session and a mutation_key was specified in the BeginTransaction][google.spanner.v1.BeginTransactionRequest].
The precommit token with the highest sequence number from
this transaction attempt should be passed to the
Commit][google.spanner.v1.Spanner.Commit] request for this
transaction.
|
cache_update |
google.cloud.spanner_v1.types.CacheUpdate
Optional. A cache update expresses a set of changes the client should incorporate into its location cache. The client should discard the changes if they are older than the data it already has. This data can be obtained in response to requests that included a RoutingHint field, but may
also be obtained by explicit location-fetching RPCs which
may be added in the future.
|