classes.rb in google-api-client-0.41.1

- old
+ new

@@ -188,14 +188,15 @@
       # The request for BeginTransaction.
       class BeginTransactionRequest
         include Google::Apis::Core::Hashable
       
         # # Transactions
-        # Each session can have at most one active transaction at a time. After the
-        # active transaction is completed, the session can immediately be
-        # re-used for the next transaction. It is not necessary to create a
-        # new session for each transaction.
+        # Each session can have at most one active transaction at a time (note that
+        # standalone reads and queries use a transaction internally and do count
+        # towards the one transaction limit). After the active transaction is
+        # completed, the session can immediately be re-used for the next transaction.
+        # It is not necessary to create a new session for each transaction.
         # # Transaction Modes
         # Cloud Spanner supports three transaction modes:
         # 1. Locking read-write. This type of transaction is the only way
         # to write data into Cloud Spanner. These transactions rely on
         # pessimistic locking and, if necessary, two-phase commit.
@@ -553,14 +554,15 @@
         # Corresponds to the JSON property `mutations`
         # @return [Array<Google::Apis::SpannerV1::Mutation>]
         attr_accessor :mutations
       
         # # Transactions
-        # Each session can have at most one active transaction at a time. After the
-        # active transaction is completed, the session can immediately be
-        # re-used for the next transaction. It is not necessary to create a
-        # new session for each transaction.
+        # Each session can have at most one active transaction at a time (note that
+        # standalone reads and queries use a transaction internally and do count
+        # towards the one transaction limit). After the active transaction is
+        # completed, the session can immediately be re-used for the next transaction.
+        # It is not necessary to create a new session for each transaction.
         # # Transaction Modes
         # Cloud Spanner supports three transaction modes:
         # 1. Locking read-write. This type of transaction is the only way
         # to write data into Cloud Spanner. These transactions rely on
         # pessimistic locking and, if necessary, two-phase commit.
@@ -3517,14 +3519,15 @@
           @read_timestamp = args[:read_timestamp] if args.key?(:read_timestamp)
         end
       end
       
       # # Transactions
-      # Each session can have at most one active transaction at a time. After the
-      # active transaction is completed, the session can immediately be
-      # re-used for the next transaction. It is not necessary to create a
-      # new session for each transaction.
+      # Each session can have at most one active transaction at a time (note that
+      # standalone reads and queries use a transaction internally and do count
+      # towards the one transaction limit). After the active transaction is
+      # completed, the session can immediately be re-used for the next transaction.
+      # It is not necessary to create a new session for each transaction.
       # # Transaction Modes
       # Cloud Spanner supports three transaction modes:
       # 1. Locking read-write. This type of transaction is the only way
       # to write data into Cloud Spanner. These transactions rely on
       # pessimistic locking and, if necessary, two-phase commit.
@@ -3770,14 +3773,15 @@
       # See TransactionOptions for more information about transactions.
       class TransactionSelector
         include Google::Apis::Core::Hashable
       
         # # Transactions
-        # Each session can have at most one active transaction at a time. After the
-        # active transaction is completed, the session can immediately be
-        # re-used for the next transaction. It is not necessary to create a
-        # new session for each transaction.
+        # Each session can have at most one active transaction at a time (note that
+        # standalone reads and queries use a transaction internally and do count
+        # towards the one transaction limit). After the active transaction is
+        # completed, the session can immediately be re-used for the next transaction.
+        # It is not necessary to create a new session for each transaction.
         # # Transaction Modes
         # Cloud Spanner supports three transaction modes:
         # 1. Locking read-write. This type of transaction is the only way
         # to write data into Cloud Spanner. These transactions rely on
         # pessimistic locking and, if necessary, two-phase commit.
@@ -3995,13 +3999,14 @@
         # NOTE: Values are automatically base64 encoded/decoded in the client library.
         # @return [String]
         attr_accessor :id
       
         # # Transactions
-        # Each session can have at most one active transaction at a time. After the
-        # active transaction is completed, the session can immediately be
-        # re-used for the next transaction. It is not necessary to create a
-        # new session for each transaction.
+        # Each session can have at most one active transaction at a time (note that
+        # standalone reads and queries use a transaction internally and do count
+        # towards the one transaction limit). After the active transaction is
+        # completed, the session can immediately be re-used for the next transaction.
+        # It is not necessary to create a new session for each transaction.
         # # Transaction Modes
         # Cloud Spanner supports three transaction modes:
         # 1. Locking read-write. This type of transaction is the only way
         # to write data into Cloud Spanner. These transactions rely on
         # pessimistic locking and, if necessary, two-phase commit.