Skip to content

DOCSP-44627: Add retry information #132

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
Oct 28, 2024
Merged
Changes from 4 commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 7 additions & 3 deletions source/fundamentals/transactions.txt
Original file line number Diff line number Diff line change
Expand Up @@ -94,9 +94,13 @@ describes these methods:
transaction was committed or ended.

* - ``and_run()``
- | Runs the given callback, then commits or ends the transaction. When you
use this method to perform a transaction, the driver automatically
handles any errors, so you can choose to omit error handling code.
- | Runs the given callback, then commits or ends the transaction. If
the callback raises an error with a ``TRANSIENT_TRANSACTION_ERROR``
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It will also retry if committing the transaction returns a transient error.

label, the driver retries the callback. If the callback raises any
other error, the driver ends the transaction and returns the error
to the caller. When you use this method to perform a transaction,
the driver automatically handles any errors, so you can choose to omit
error handling code.
|
| Because the callback returns a future and can be run multiple
times, the Rust language closure borrowing rules for captured
Expand Down
Loading