Connection errors don't propagate to Query callback

[allenc256]

Looking at query.coffee, it looks like if the underlying connection emits an 'error' event (e.g., because of network connectivity issues), the error event never makes it to the callback on Query. Is this intentional?

Basically, I'm using the callback API and was expecting this to catch all errors, but it isn't. My workaround is to also add a listener on 'error' to the connection, but seems like the API would be nicer if users didn't have to do this ...

[wvanbergen]

Some errors are thrown on the connection, while others are thrown on the query. What is the actual code you are using?

[wvanbergen]

That being said, the error handling in this library certainly could be improved. However, this issue is a bit vague for me to act upon.