Google Cloud Spanner v1 API - Enum TransactionOptions.Types.IsolationLevel (5.0.0-beta06)

Stay organized with collections Save and categorize content based on your preferences.

All reads performed during the transaction observe a consistent snapshot of the database, and the transaction will only successfully commit in the absence of conflicts between its updates and any concurrent updates that have occurred since that snapshot. Consequently, in contrast to SERIALIZABLE transactions, only write-write conflicts are detected in snapshot transactions.

This isolation level does not support Read-only and Partitioned DML transactions.

When REPEATABLE_READ is specified on a read-write transaction, the locking semantics default to OPTIMISTIC.

All transactions appear as if they executed in a serial order, even if some of the reads, writes, and other operations of distinct transactions actually occurred in parallel. Spanner assigns commit timestamps that reflect the order of committed transactions to implement this property. Spanner offers a stronger guarantee than serializability called external consistency. For further details, please refer to https://cloud.google.com/spanner/docs/true-time-external-consistency#serializability.

Default value.

If the value is not specified, the SERIALIZABLE isolation level is used.