id may be used to identify the transaction in subsequent
[Read][google.spanner.v1.Spanner.Read],
[ExecuteSql][google.spanner.v1.Spanner.ExecuteSql],
[Commit][google.spanner.v1.Spanner.Commit], or
[Rollback][google.spanner.v1.Spanner.Rollback] calls.
Single-use read-only transactions do not have IDs, because
single-use transactions do not support multiple requests.
For snapshot read-only transactions, the read timestamp chosen
for the transaction. Not returned by default: see
[TransactionOptions.ReadOnly.return_read_timestamp][google.spanner.v1.TransactionOptions.ReadOnly.return_read_timestamp].
A timestamp in RFC3339 UTC "Zulu" format, accurate to nanoseconds.
Example: "2014-10-02T15:01:23.045123456Z".
[[["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\u003eThe \u003ccode\u003eTransaction\u003c/code\u003e class in the Google Cloud Spanner v1 API represents a transaction within the Spanner database.\u003c/p\u003e\n"],["\u003cp\u003eThis documentation covers versions of \u003ccode\u003eGoogle.Cloud.Spanner.V1\u003c/code\u003e, including beta releases like \u003ccode\u003e5.0.0-beta05\u003c/code\u003e, with versions available from \u003ccode\u003e3.5.0\u003c/code\u003e to \u003ccode\u003e5.0.0-beta05\u003c/code\u003e and version \u003ccode\u003e4.2.0\u003c/code\u003e being specifically covered here.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eTransaction\u003c/code\u003e class implements interfaces such as \u003ccode\u003eIMessage\u003c/code\u003e, \u003ccode\u003eIEquatable\u003c/code\u003e, \u003ccode\u003eIDeepCloneable\u003c/code\u003e, and \u003ccode\u003eIBufferMessage\u003c/code\u003e, providing functionalities like message handling, equality checks, deep cloning, and buffer message support.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003eTransaction\u003c/code\u003e objects can be constructed using a default constructor or a copy constructor which takes in another \u003ccode\u003eTransaction\u003c/code\u003e object, and it has properties such as \u003ccode\u003eId\u003c/code\u003e for identifying the transaction and \u003ccode\u003eReadTimestamp\u003c/code\u003e for read-only transactions.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eId\u003c/code\u003e property of a transaction is of type \u003ccode\u003eByteString\u003c/code\u003e, and the \u003ccode\u003eReadTimestamp\u003c/code\u003e property is of type \u003ccode\u003eTimestamp\u003c/code\u003e, which represents the read timestamp for snapshot read-only transactions.\u003c/p\u003e\n"]]],[],null,[]]
