Anton Komarov
Anton Komarov
**Describe the bug** A clear and concise description of what the bug is. **To Reproduce** Steps to reproduce the behavior: 1. View document `{ "username": "[email protected]", "grps": [ "group-id-1", "group-id-2"...
It would be really helpful to have such option for the connection pool. Because it should help to work with 'persistent' connections more carefully with keepAlive option enabled. It already...
Thanks for your work. We are using the connection pool of mysql2 in production in CloudRun with ["CPU is always allocated"](https://cloud.google.com/run/docs/configuring/cpu-allocation#setting) (i.e. simply say, it is a regular nodejs app)...
I noticed that with some configuration of Connection Pool the Node process can't stop working and just hang. In my case, it appears in mocha tests when mocha process can't...
Previously, in our solution, we closed a connection on every SQL statement or SQL error and worked without connection pool. For now, we are trying to migrate to the connection...