@@ -310,25 +310,33 @@ ensure your data maintains consistent. If the following errors occur, the
310
310
transaction must be retried:
311
311
312
312
- ``TransientTransactionError``: Raised if a write operation encounters an error
313
- before the driver commits the transaction.
313
+ before the driver commits the transaction. To learn more about this error
314
+ type, see the :manual:`TransientTransactionError description
315
+ </core/transactions-in-applications/#transienttransactionerror>` on the Drivers API page in the
316
+ Server manual.
314
317
- ``UnknownTransactionCommitResult``: Raised if the commit operation encounters
315
- an error.
318
+ an error. To learn more about this error type, see the
319
+ :manual:`UnknownTransactionCommitResult description
320
+ </core/transactions-in-applications/#unknowntransactioncommitresult>` on the Drivers API page in the
321
+ Server manual.
322
+
323
+ The Convenient Transaction API incorporates retry logic for these error types,
324
+ so the driver automatically retries the transaction until there is a successful
325
+ commit.
326
+
327
+ Core API Error Error Handling
328
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
316
329
317
330
If you are using the Core API to perform a transaction, you must implement the
318
- error-handling logic into your application. To do so, you must create the following functions:
331
+ error-handling logic into your application. To do so, you must create the
332
+ following functions that run until there is a successful commit or a different
333
+ error:
319
334
320
335
- A function that retries the entire transaction when the driver encounters a
321
- ``TransientTransactionError``
336
+ ``TransientTransactionError``
322
337
- A function that retries the commit operation when the driver encounters an
323
338
``UnknownTransactionCommitResult``
324
339
325
- These functions should continue to retry the operation until there is a
326
- successful commit or a different error. For an example of this retry
327
- logic, see the :manual:`Core API section
340
+ For an example of this retry logic, see the :manual:`Core API section
328
341
</core/transactions-in-applications/#core-api>` on the Drivers API page in the
329
- Server manual.
330
-
331
- The Convenient Transaction API incorporates retry logic for these error types,
332
- so the driver automatically retries the transaction until there is a successful
333
- commit. You do not have to explicitly declare functions for the API to retry
334
- transaction operations when the driver produces these errors.
342
+ Server manual.
0 commit comments