- 3.46.0 (latest)
- 3.45.0
- 3.44.0
- 3.43.0
- 3.42.0
- 3.41.0
- 3.40.1
- 3.39.0
- 3.38.0
- 3.37.0
- 3.36.0
- 3.35.1
- 3.34.0
- 3.33.0
- 3.32.0
- 3.31.0
- 3.30.0
- 3.29.0
- 3.28.0
- 3.27.1
- 3.26.0
- 3.25.0
- 3.24.0
- 3.23.0
- 3.22.2
- 3.21.0
- 3.20.0
- 3.19.0
- 3.18.0
- 3.17.0
- 3.16.0
- 3.15.1
- 3.14.1
- 3.13.0
- 3.12.1
- 3.11.1
- 3.10.0
- 3.9.0
- 3.8.0
- 3.7.0
- 3.6.0
- 3.5.0
- 3.4.0
- 3.3.0
- 3.2.0
- 3.1.0
- 3.0.0
- 2.1.1
- 2.0.0
- 1.19.3
- 1.18.0
- 1.17.1
- 1.16.0
- 1.15.1
- 1.14.0
- 1.13.0
- 1.12.0
- 1.11.0
- 1.10.0
ReadOnly(mapping=None, *, ignore_unknown_fields=False, **kwargs)
Message type to initiate a read-only transaction.
Attributes | |
---|---|
Name | Description |
strong |
bool
Read at a timestamp where all previously committed transactions are visible. |
min_read_timestamp |
google.protobuf.timestamp_pb2.Timestamp
Executes all reads at a timestamp >= min_read_timestamp .
This is useful for requesting fresher data than some
previous read, or data that is fresh enough to observe the
effects of some previously committed transaction whose
timestamp is known.
Note that this option can only be used in single-use
transactions.
A timestamp in RFC3339 UTC "Zulu" format, accurate to
nanoseconds. Example: "2014-10-02T15:01:23.045123456Z" .
|
max_staleness |
google.protobuf.duration_pb2.Duration
Read data at a timestamp >= NOW - max_staleness seconds.
Guarantees that all writes that have committed more than the
specified number of seconds ago are visible. Because Cloud
Spanner chooses the exact timestamp, this mode works even if
the client's local clock is substantially skewed from Cloud
Spanner commit timestamps.
Useful for reading the freshest data available at a nearby
replica, while bounding the possible staleness if the local
replica has fallen behind.
Note that this option can only be used in single-use
transactions.
|
read_timestamp |
google.protobuf.timestamp_pb2.Timestamp
Executes all reads at the given timestamp. Unlike other modes, reads at a specific timestamp are repeatable; the same read at the same timestamp always returns the same data. If the timestamp is in the future, the read will block until the specified timestamp, modulo the read's deadline. Useful for large scale consistent reads such as mapreduces, or for coordinating many reads against a consistent snapshot of the data. A timestamp in RFC3339 UTC "Zulu" format, accurate to nanoseconds. Example: "2014-10-02T15:01:23.045123456Z" .
|
exact_staleness |
google.protobuf.duration_pb2.Duration
Executes all reads at a timestamp that is exact_staleness old. The timestamp is chosen soon after
the read is started.
Guarantees that all writes that have committed more than the
specified number of seconds ago are visible. Because Cloud
Spanner chooses the exact timestamp, this mode works even if
the client's local clock is substantially skewed from Cloud
Spanner commit timestamps.
Useful for reading at nearby replicas without the
distributed timestamp negotiation overhead of
max_staleness .
|
return_read_timestamp |
bool
If true, the Cloud Spanner-selected read timestamp is included in the Transaction][google.spanner.v1.Transaction]
message that describes the transaction.
|