-
Notifications
You must be signed in to change notification settings - Fork 443
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
Release 1.15.0 #477
Comments
Great contributions! Thanks for all your effort. |
This is great @arthurschreiber!
Can we merge the unit tests for Multi Subnet Failover Feature (#362) |
@arthurschreiber Is there any ETA on this being released? Would love to have the multiSubnetFailover feature! |
There is one last thing missing before we can push out a release, and that's compatibility between Once that is resolved, I'll push the new tedious release ASAP. |
@arthurschreiber Just want to check up on this again, real excited for this feature! Is there anything I could do to help move this along? |
@arthurschreiber Please, consider reviewing #501 for this release. It is simple. It works and should be an available option. |
Any progress on new release ? |
I plan to release the next version of
tedious
,1.15.0
"Alive and Kicking" soon.Here's the changelog so far:
What's New
Multi Subnet Failover #362
tedious
now 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,tedious
will now sequentially try to connect to each of them, and will stop after the first successful connection. There's now also support for themultiSubnetFailover
connection option, which allows to connect to all resolved IP addresses in parallel and will use whichever connection was established first. Thanks @chrislukkk!Add
options.trustServerCertificate
. #419 When establishing an encrypted connection to a server,tedious
never actually verified the certificate presented by the server. As this is probably not a good idea from a security standpoint, there is a newtrustServerCertificate
connection option that you can set tofalse
to enforce certificate verification. The default behaviour did not change, but will in a future release. Thanks @SimonHooker!Fixed
Currently inTransaction state on Connection is maintained based on the #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!
fix problems with encrypted data and NTLM login. #367 Encrypted connections and NTLM authentication didn't work together, at all - but now they do! Thanks @leerlemoniii and @mcrummey!
NTLM authentication requires domain to be upper case #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!
Improve performance of queries that select GUID columns. #440 guidToArray performance tuning #443 Parsing and writing the contents of GUID columns was pretty slow. Now it's many times faster! Thanks @jdanyow!
Connection class constructor keeps a reference of and modifies passed… #445 The configuration object that was passed to the
Connection
constructor was modified in multiple places. That was pretty careless and unexpected, sotedious
now will keep an internal copy of the configuration. Thanks @tvrprasad!Did I miss anything important?
/cc @tvrprasad @SaloniSonpal @patriksimek
The text was updated successfully, but these errors were encountered: