- 1.104.1 (latest)
- 1.104.0
- 1.103.0
- 1.102.0
- 1.101.0
- 1.100.0
- 1.98.0
- 1.97.0
- 1.96.0
- 1.95.0
- 1.94.0
- 1.93.1
- 1.92.1
- 1.91.0
- 1.90.0
- 1.89.0
- 1.88.0
- 1.87.0
- 1.86.0
- 1.85.0
- 1.84.0
- 1.83.0
- 1.82.0
- 1.81.0
- 1.80.0
- 1.79.0
- 1.78.0
- 1.77.0
- 1.76.1
- 1.68.0
- 1.67.0
- 1.66.0
- 1.65.0
- 1.64.0
- 1.63.2
- 1.62.1
- 1.61.0
- 1.60.0
- 1.59.0
- 1.58.4
- 1.57.0
- 1.56.0
- 1.55.0
- 1.54.2
Reference documentation and code samples for the Cloud Spanner V1 Client class IsolationLevel.
IsolationLevel is used when setting isolation_level for a transaction.
Protobuf type google.spanner.v1.TransactionOptions.IsolationLevel
Namespace
Google \ Cloud \ Spanner \ V1 \ TransactionOptionsMethods
static::name
| Parameter | |
|---|---|
| Name | Description |
value |
mixed
|
static::value
| Parameter | |
|---|---|
| Name | Description |
name |
mixed
|
Constants
ISOLATION_LEVEL_UNSPECIFIED
Value: 0Default value.
If the value is not specified, the SERIALIZABLE isolation level is
used.
Generated from protobuf enum ISOLATION_LEVEL_UNSPECIFIED = 0;
SERIALIZABLE
Value: 1All 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 more information, see TrueTime and external consistency.
Generated from protobuf enum SERIALIZABLE = 1;
REPEATABLE_READ
Value: 2All reads performed during the transaction observe a consistent snapshot
of the database, and the transaction is only successfully committed 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.
Generated from protobuf enum REPEATABLE_READ = 2;