We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Now transaction logic does not block the row in DB. So double spendings and related issues may occur.
Need to implement pessimistic locking (like described in this blog post: https://hakibenita.com/how-to-manage-concurrency-in-django-models) With the use of related fields lock.
So that every transaction operation (process, substitute, decline) would block account while processing.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Now transaction logic does not block the row in DB. So double spendings and related issues may occur.
Need to implement pessimistic locking (like described in this blog post: https://hakibenita.com/how-to-manage-concurrency-in-django-models) With the use of related fields lock.
So that every transaction operation (process, substitute, decline) would block account while processing.
The text was updated successfully, but these errors were encountered: