Indicates how to choose the timestamp at which to read the data for Cloud Spanner read-only transactions.
If your application can tolerate some staleness when reading data, you can use a stale read,
which can execute much faster when compared to reading the latest data.
Executes all reads at a timestamp that is duration
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 MaxStaleness.
MaxStaleness
Read data at a timestamp >= NOW - duration. 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.
MinReadTimestamp
Executes all reads at a timestamp >= minReadTimestamp.
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.
ReadTimestamp
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.
Strong
Read at a timestamp where all previously committed transactions
are visible.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-07 UTC."],[[["\u003cp\u003eThis document details the \u003ccode\u003eTimestampBoundMode\u003c/code\u003e enum for Cloud Spanner read-only transactions, with options to manage data staleness.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eTimestampBoundMode\u003c/code\u003e enum has five fields: \u003ccode\u003eExactStaleness\u003c/code\u003e, \u003ccode\u003eMaxStaleness\u003c/code\u003e, \u003ccode\u003eMinReadTimestamp\u003c/code\u003e, \u003ccode\u003eReadTimestamp\u003c/code\u003e, and \u003ccode\u003eStrong\u003c/code\u003e, each defining how to select the read timestamp.\u003c/p\u003e\n"],["\u003cp\u003eStale reads, achieved with options like \u003ccode\u003eExactStaleness\u003c/code\u003e and \u003ccode\u003eMaxStaleness\u003c/code\u003e, can improve read speed by allowing some data staleness, which is described in more detail in the enum descriptions.\u003c/p\u003e\n"],["\u003cp\u003eThe latest version available for the Google.Cloud.Spanner.Data package is 5.0.0-beta05, but multiple previous versions of the package are also documented.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eStrong\u003c/code\u003e field, within the \u003ccode\u003eTimestampBoundMode\u003c/code\u003e, provides the freshest data, where all previously committed transactions are visible.\u003c/p\u003e\n"]]],[],null,[]]
