Repository navigation
docs: link projects that use the Transaction use-case shape - #73
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The "Transaction management" example in the README now links to three projects that use the same use-case shape: fastapi-sqlalchemy-template, litestar-sqlalchemy-template and chat-app. All three run with
pool_pre_pingoff and rely onpostgres_retryfor connections that died while idle in the pool. The templates switched to this setup in modern-python/fastapi-sqlalchemy-template#88 and modern-python/litestar-sqlalchemy-template#65.The links are absolute, because the README is also the PyPI description. All three return 200.