No error emitted on failed connection

[MatthewPhinney]

If a SQL Server database is configured to use encrypted connections, the client must specify encrypt: true in the tedious connection config. If the client does not specify encrypt: true, the connection to the database fails, but the connection object does not emit an error event.
The connection should emit an error, so the client can handle it appropriately.

Here is sample output from a connection attempt:

Debug event:  connected to <db-using-encrypted-connections>
Debug event:  State change: Connecting -> SentPrelogin
Debug event:  State change: SentPrelogin -> SentTLSSSLNegotiation
Debug event:  socket ended
Debug event:  State change: SentTLSSSLNegotiation -> Final
End event:    undefined
Debug event:  State is already Final
Debug event:  socket ended
Debug event:  connection to <db-using-encrypted-connections> closed

Incidentally, TLS.createSecurePair is deprecated. Is there any plan to update this code?

[tvrprasad]

Thanks for reporting.
Sent pull request to address this: #514

[tvrprasad]

About the deprecated createSecurePair, there is a open issue for that - #135. Need someone inspired to take it on :-)

[MatthewPhinney]

Thanks for the quick response -- please let me know when a new version (including the changes in #514) is published on npm.

[tvrprasad]

Stay tuned :-)

[tvrprasad]

The PR is merged. Closing the issue.