You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 2, 2021. It is now read-only.
When a database transaction fails, it might be a good idea to retry it. Some initial thoughts and questions:
What are the most common reasons a transaction would fail?
Do we want to retry all failed transactions or only when the failure was something we know has a possibility of working on another try (e.g. deadlocks)?
What should the limit on the number of retries be?
Should retry logic be part of application logic or encapsulated as part of the database layer itself? (I'm not sure if Diesel has any sort of automatic retrying feature that we might leverage, if we want to go for the latter.)
The text was updated successfully, but these errors were encountered:
Continued from #121.
When a database transaction fails, it might be a good idea to retry it. Some initial thoughts and questions:
The text was updated successfully, but these errors were encountered: