-
Notifications
You must be signed in to change notification settings - Fork 261
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
fix concurrency issues of parallel transactions (#327) #328
Conversation
looks good, no? |
@tomchristie take a look at this PR please |
Co-authored-by: Egor Panfilov <[email protected]>
I'm happy to help out with expanding the maintainers team as needed, but I don't have any time to invest in |
@goteguru Please run linting/formatting scripts in the |
Thx for the honest reply. In the meantime I've replaced Maybe it would be nice to list the active project maintainers (w/ commit right) in the project page. |
I already did manually (all tests are passed), but I run them again for isort. Please consider recommended best practices while working from a windows machine: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you @goteguru
fix concurrency of parallel transactions (encode#328)
This is the proposed solution for async transaction execution failure (see #327 )
Tests are running fine for postgres, mysql, sqlite.
I had to change the test tests/test_databases.py because it incorrectly expects database.transaction() to use the same connection as the connection context around it, which is certainly not true (and actually the part of the problem). If I acquire a connection, I have to use that connection for a transaction. (Requesting the database directly may give any other connection from the pool).
All comments are welcome.