Specifying the mode of the transaction can help to improve throughput, as it
provides additional information about the intent (or lack of intent, in the
case of a read only transaction) to perform a write as part of the
transaction.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2022-09-30 UTC."],[[["Datastore transactions have different modes that can impact performance."],["Specifying a transaction's mode helps optimize throughput by indicating the intent to write or read."],["The `READ_ONLY` mode (value: 1) is for transactions that only read data."],["The `READ_WRITE` mode (value: 2) is for transactions that involve writing data."],["The `UNKNOWN` mode (value: 0) represents a transaction mode where the intent is not specified."]]],[]]
View source on GitHub