1.15.0 (Alive and Kicking)
What's New
- #362
tediousnow has better support for SQLServer instances configured for High Availability! If the DNS name for the SQLServer instance you're connecting to resolves to multiple IP addresses,tediouswill now sequentially try to connect to each of them, and will stop after the first successful connection. There's now also support for themultiSubnetFailoverconnection option, which allows to connect to all resolved IP addresses in parallel and will use whichever connection was established first. Thanks @chrislukkk and @tvrprasad! - #419 When establishing an encrypted connection to a server,
tediousnever actually verified the certificate presented by the server. As this is probably not a good idea from a security standpoint, there is a newtrustServerCertificateconnection option that you can set tofalseto enforce certificate verification. The default behaviour did not change, but will in a future release. Thanks @SimonHooker! - #503 The
datefirstconnection option can now modified when opening a new connection via thedatefirstconnection option. Thanks @edwardsmit! - #501 The
arithabortconnection option can now modified when opening a new connection via theenableArithAbortconnection option. Thanks @carlosman! - #505 If a connection is closed prematurely, in-flight requests will have their callback invoked with a
RequestErrorinstead of never being called. Thanks @tvrprasad! - #489
RequestErrorandConnectionErrorare now exposed as part of thetediouspackage. Thanks @jeffrosenberg!
Fixed
- #461 We accidentally broke support for TDS 7.1 (used by SQLServer 2000) a few versions ago. If you're still running software from the year 2000, rejoice - TDS 7.1 support is back! Thanks @tvrprasad!
- #367 Encrypted connections and NTLM authentication didn't work together, at all - but now they do! Thanks @leerlemoniii and @mcrummey!
- #417 When authenticating via NTLM, the domain name was sent to the server as provided in the connection options. As it turns out, NTLM prefers domain names to be specified in upper case, so that's what we're doing now. Thanks @tvrprasad!
- #440 #443 Parsing and writing the contents of GUID columns was pretty slow. Now it's many times faster! Thanks @jdanyow!
- #445 The configuration object that was passed to the
Connectionconstructor was modified in multiple places. That was pretty careless and unexpected, sotediousnow will keep an internal copy of the configuration. Thanks @tvrprasad! - #504 Range validation on BigInt data type to prevent silent data corruption. JavaScript only supports precision to 53 bits where BigInt is 64 bits. This used to cause imprecise data being inserted, now this is detected and an error message with work-around presented. Thanks @tvrprasad!
- #530 The per-request timeout was not cancelled directly after receiving the data (as defined by the TDS specification), so when receiving a large amount of data the request might time out during processing. This will not happen anymore thanks to @chdh!
- #517 The millisecond value for
DateTimefields is now getting rounded down correctly. Thanks @fuga! - #514 Failure of establishing an encrypted connection is no longer silently ignored. Thanks @tvrprasad!
Note
This will be the last version of tedious to support Node.js versions < 4.