Class Transaction (2.19.0)

Version 2.19.0

• 2.32.0-rc (latest)
• 2.31.0
• 2.30.0
• 2.29.0
• 2.28.0
• 2.27.0
• 2.26.0
• 2.25.1
• 2.24.0
• 2.23.0
• 2.22.0
• 2.21.0
• 2.20.0
• 2.19.0
• 2.18.0
• 2.17.0
• 2.16.0
• 2.15.1
• 2.14.0
• 2.13.0
• 2.12.0
• 2.11.0

The representation of a Cloud Spanner transaction.

A transaction is a set of reads and writes that execute atomically at a single logical point in time across the columns/rows/tables in a database. Those reads and writes are grouped by passing them the same Transaction.

All reads/writes in the transaction must be executed within the same session, and that session may have only one transaction active at a time.

Spanner supports these transaction modes:

• ReadOnly. Provides guaranteed consistency across several reads, but does not allow writes. Can be configured to read at timestamps in the past. Does not need to be committed and does not take locks.
• ReadWrite. Supports reading and writing data at a single point in time. Uses pessimistic locking and, if necessary, two-phase commit. May abort, requiring the application to rerun.
• SingleUse. A restricted form of a ReadOnly transaction where Spanner chooses the read timestamp.

Constructors

Transaction(ReadOnlyOptions)

Construction of read-only and read-write transactions.

Note: This is a lazy evaluated operation. No RPCs are made as part of creating a Transaction object. Instead, the first request to the server (for example as part of a ExecuteQuery() call) will also create the transaction.

Parameter
Name	Description
opts	ReadOnlyOptions

Transaction(ReadWriteOptions)

Construction of read-only and read-write transactions.

Note: This is a lazy evaluated operation. No RPCs are made as part of creating a Transaction object. Instead, the first request to the server (for example as part of a ExecuteQuery() call) will also create the transaction.

Parameter
Name	Description
opts	ReadWriteOptions

Transaction(Transaction const &, ReadWriteOptions)

Construction of read-only and read-write transactions.

Note: This is a lazy evaluated operation. No RPCs are made as part of creating a Transaction object. Instead, the first request to the server (for example as part of a ExecuteQuery() call) will also create the transaction.

Parameters
Name	Description
txn	Transaction const &
opts	ReadWriteOptions

Transaction(Transaction &&)

Regular value type, supporting copy, assign, move.

Parameter
Name	Description
	Transaction &&

Transaction(Transaction const &)

Regular value type, supporting copy, assign, move.

Parameter
Name	Description
	Transaction const &

Operators

operator=(Transaction &&)

Regular value type, supporting copy, assign, move.

Parameter
Name	Description
	Transaction &&

Returns
Type	Description
Transaction &

operator=(Transaction const &)

Regular value type, supporting copy, assign, move.

Parameter
Name	Description
	Transaction const &

Returns
Type	Description
Transaction &