-
Notifications
You must be signed in to change notification settings - Fork 2.5k
Pool connection failure doesn't emit error event #941
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
Comments
I think it will be fixed with use |
Ah, I see what you're saying: the connection error is only propagated to the returned query if you are using the callback interface. This is a bug indeed. |
I'm sorry to less description. I want to clarification: |
Right, I understood what you were asking, @topia :) The answer is that it's a bug and I have to fix it :) |
Thank you very match for fixing this! |
No problem! I just published it to npm as 2.5.3 :) |
Pool.query doesn't emit error event, when it failed with connection error.
index.js
package.json
expected
actual
The text was updated successfully, but these errors were encountered: