Enum TransactionOptions.IsolationLevel (6.88.0)

Version latest

• 6.88.0 (latest)
• 6.87.0
• 6.86.0
• 6.85.0
• 6.83.0
• 6.82.0
• 6.80.1
• 6.79.0
• 6.77.0
• 6.74.1
• 6.72.0
• 6.71.0
• 6.69.0
• 6.68.0
• 6.66.0
• 6.65.1
• 6.62.0
• 6.60.0
• 6.58.0
• 6.57.0
• 6.56.0
• 6.55.0
• 6.54.0
• 6.53.0
• 6.52.1
• 6.51.0
• 6.50.1
• 6.49.0
• 6.25.1
• 6.24.0
• 6.23.4
• 6.22.0
• 6.21.2
• 6.20.0
• 6.19.1
• 6.18.0
• 6.17.4
• 6.14.1

public enum TransactionOptions.IsolationLevel extends Enum<TransactionOptions.IsolationLevel> implements ProtocolMessageEnum

IsolationLevel is used when setting isolation_level for a transaction.

Protobuf enum google.spanner.v1.TransactionOptions.IsolationLevel

Implements

ProtocolMessageEnum

Inherited Members

Enum.<T>valueOf(Class<T>,String)

Enum.clone()

Enum.compareTo(E)

Enum.equals(Object)

Enum.finalize()

Enum.getDeclaringClass()

Enum.hashCode()

Enum.name()

Enum.ordinal()

Enum.toString()

Object.getClass()

Object.notify()

Object.notifyAll()

Object.wait()

Object.wait(long)

Object.wait(long,int)

Static Fields
Name	Description
ISOLATION_LEVEL_UNSPECIFIED	Default value. If the value is not specified, the SERIALIZABLE isolation level is used. ISOLATION_LEVEL_UNSPECIFIED = 0;
ISOLATION_LEVEL_UNSPECIFIED_VALUE	Default value. If the value is not specified, the SERIALIZABLE isolation level is used. ISOLATION_LEVEL_UNSPECIFIED = 0;
REPEATABLE_READ	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. REPEATABLE_READ = 2;
REPEATABLE_READ_VALUE	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. REPEATABLE_READ = 2;
SERIALIZABLE	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. SERIALIZABLE = 1;
SERIALIZABLE_VALUE	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. SERIALIZABLE = 1;
UNRECOGNIZED

Static Methods
Name	Description
forNumber(int value)
getDescriptor()
internalGetValueMap()
valueOf(Descriptors.EnumValueDescriptor desc)
valueOf(int value)	Deprecated. Use #forNumber(int) instead.
valueOf(String name)
values()

Methods
Name	Description
getDescriptorForType()
getNumber()
getValueDescriptor()