-
Notifications
You must be signed in to change notification settings - Fork 466
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
Allow windows users to choose their own driver. #1428
Comments
Absolutely, this has been something I've thought about too, but given lack of demand (and lack of production environment for me to test in), I've held back. If you're prepared to make a contribution, would you mind creating a PR? We may have to consider how we can test these various drivers in CI |
1 task
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Right now windows users are stuck with the 'SQL Server Native Client 11.0' driver. Why not let developers choose whether we want the ODBC driver or the Native Client? The biggest driver for me is that the SQL Server Native Client doesn't support column encryption.
Also adding ColumnEncryption to
CONNECTION_STRING_PORT
andCONNECTION_STRING_NAMED_INSTANCE
would to be super cool too.Expected behaviour:
Encrypted columns to return their decrypted form.
Actual behaviour:
Encrypted columns return their encrypted byte code.
Configuration:
Software versions
Here's the modified connection-pool.js necessary to make the requested changes to the code.
connection-pool.js
The text was updated successfully, but these errors were encountered: