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
Because why not, especially when using as a context manager?
It doesn't really go against the main requirement in #206 (comment):
it should not be possible to (unknowingly) leak connections by using the same Reader object from multiple threads
For comparison, SQLAlchemy allows "reviving" an Engine as well.
The text was updated successfully, but these errors were encountered:
Resolved in #206 / 05c1260.
Sorry, something went wrong.
No branches or pull requests
Because why not, especially when using as a context manager?
It doesn't really go against the main requirement in #206 (comment):
For comparison, SQLAlchemy allows "reviving" an Engine as well.
The text was updated successfully, but these errors were encountered: