You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 and CONNECTION_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.
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
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: