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
PoolConnectionHolder.connect: It seems that self._connect_kwargs is missed in self._pool._connect arguments when self._pool._working_addr is not None
The text was updated successfully, but these errors were encountered:
Yeah, that's intentional. Have you found any bugs caused by that?
Sorry, something went wrong.
Yes, statement_cache_size=0 does not work when connection created from pool with defined working_addr.
Then it's a bug. I'll look into it.
PR #130 will fix this. 0.11.0 will be released soon.
0.11.0 has been released yesterday, please upgrade!
No branches or pull requests
PoolConnectionHolder.connect:
It seems that self._connect_kwargs is missed in self._pool._connect arguments when self._pool._working_addr is not None
The text was updated successfully, but these errors were encountered: