From cd4ddfe95b63ae3ac5e8b8c584f0cb360a94722c Mon Sep 17 00:00:00 2001 From: Saurabh Chaturvedi Date: Sat, 18 Jan 2020 18:58:40 +0530 Subject: [PATCH 1/2] Fix typo in class scheduling Python example --- documentation/sphinx/source/class-scheduling.rst | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/documentation/sphinx/source/class-scheduling.rst b/documentation/sphinx/source/class-scheduling.rst index c13678a23f..edb60dc439 100644 --- a/documentation/sphinx/source/class-scheduling.rst +++ b/documentation/sphinx/source/class-scheduling.rst @@ -136,7 +136,7 @@ If instead you pass a :class:`Transaction` for the ``tr`` parameter, the transac Note that by default, the operation will be retried an infinite number of times and the transaction will never time out. It is therefore recommended that the client choose a default transaction retry limit or timeout value that is suitable for their application. This can be set either at the transaction level using the ``set_retry_limit`` or ``set_timeout`` transaction options or at the database level with the ``set_transaction_retry_limit`` or ``set_transaction_timeout`` database options. For example, one can set a one minute timeout on each transaction and a default retry limit of 100 by calling:: db.options.set_transaction_timeout(60000) # 60,000 ms = 1 minute - db.options.set_retry_limit(100) + db.options.set_transaction_retry_limit(100) Making some sample classes -------------------------- @@ -350,7 +350,7 @@ Here's the code for the scheduling tutorial:: db = fdb.open() db.options.set_transaction_timeout(60000) # 60,000 ms = 1 minute - db.options.set_retry_limit(100) + db.options.set_transaction_retry_limit(100) scheduling = fdb.directory.create_or_open(db, ('scheduling',)) course = scheduling['class'] attends = scheduling['attends'] From d1c823b3d710d509e303fb5c66de18e350fea07e Mon Sep 17 00:00:00 2001 From: Saurabh Chaturvedi Date: Thu, 30 Jan 2020 19:10:08 +0530 Subject: [PATCH 2/2] Fix transaction retry typo for other lang tutorials --- documentation/sphinx/source/class-scheduling-go.rst | 2 +- documentation/sphinx/source/class-scheduling-java.rst | 4 ++-- documentation/sphinx/source/class-scheduling-ruby.rst | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/documentation/sphinx/source/class-scheduling-go.rst b/documentation/sphinx/source/class-scheduling-go.rst index a0d103769b..87080ac374 100644 --- a/documentation/sphinx/source/class-scheduling-go.rst +++ b/documentation/sphinx/source/class-scheduling-go.rst @@ -229,7 +229,7 @@ Furthermore, this version can only be called with a ``Database``, making it impo Note that by default, the operation will be retried an infinite number of times and the transaction will never time out. It is therefore recommended that the client choose a default transaction retry limit or timeout value that is suitable for their application. This can be set either at the transaction level using the ``SetRetryLimit`` or ``SetTimeout`` transaction options or at the database level with the ``SetTransactionRetryLimit`` or ``SetTransactionTimeout`` database options. For example, one can set a one minute timeout on each transaction and a default retry limit of 100 by calling:: db.Options().SetTransactionTimeout(60000) // 60,000 ms = 1 minute - db.Options().SetRetryLimit(100) + db.Options().SetTransactionRetryLimit(100) Making some sample classes -------------------------- diff --git a/documentation/sphinx/source/class-scheduling-java.rst b/documentation/sphinx/source/class-scheduling-java.rst index 75db289e1a..23240100c6 100644 --- a/documentation/sphinx/source/class-scheduling-java.rst +++ b/documentation/sphinx/source/class-scheduling-java.rst @@ -157,7 +157,7 @@ If instead you pass a :class:`Transaction` for the :class:`TransactionContext` p Note that by default, the operation will be retried an infinite number of times and the transaction will never time out. It is therefore recommended that the client choose a default transaction retry limit or timeout value that is suitable for their application. This can be set either at the transaction level using the ``setRetryLimit`` or ``setTimeout`` transaction options or at the database level with the ``setTransactionRetryLimit`` or ``setTransactionTimeout`` database options. For example, one can set a one minute timeout on each transaction and a default retry limit of 100 by calling:: db.options().setTransactionTimeout(60000); // 60,000 ms = 1 minute - db.options().setRetryLimit(100); + db.options().setTransactionRetryLimit(100); Making some sample classes -------------------------- @@ -444,7 +444,7 @@ Here's the code for the scheduling tutorial: fdb = FDB.selectAPIVersion(620); db = fdb.open(); db.options().setTransactionTimeout(60000); // 60,000 ms = 1 minute - db.options().setRetryLimit(100); + db.options().setTransactionRetryLimit(100); } // Generate 1,620 classes like '9:00 chem for dummies' diff --git a/documentation/sphinx/source/class-scheduling-ruby.rst b/documentation/sphinx/source/class-scheduling-ruby.rst index 345678887c..45c6534097 100644 --- a/documentation/sphinx/source/class-scheduling-ruby.rst +++ b/documentation/sphinx/source/class-scheduling-ruby.rst @@ -126,7 +126,7 @@ If instead you pass a :class:`Transaction` for the ``db_or_tr`` parameter, the t Note that by default, the operation will be retried an infinite number of times and the transaction will never time out. It is therefore recommended that the client choose a default transaction retry limit or timeout value that is suitable for their application. This can be set either at the transaction level using the ``set_retry_limit`` or ``set_timeout`` transaction options or at the database level with the ``set_transaction_retry_limit`` or ``set_transaction_timeout`` database options. For example, one can set a one minute timeout on each transaction and a default retry limit of 100 by calling:: @db.options.set_transaction_timeout(60000) # 60,000 ms = 1 minute - @db.options.set_retry_limit(100) + @db.options.set_transaction_retry_limit(100) Making some sample classes --------------------------