-
Notifications
You must be signed in to change notification settings - Fork 68
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
Always Encrypted - get it working #56
Comments
Did you have any success getting this to work @lokmannicholas ? |
Does this driver even claim support for AE? It looks like this PR never got in: |
it doesn't work, i am finding someone to make it work together @@ |
@shueybubbles Is it possible to raise some attention on this? Always Encrypted is in a bad place right now with language support outside of the C#/.NET/Java ecosystems. *Open source SQL drivers have MSSQL as an afterthought, and ODBC C++ wrappers have very mixed support (such as in the case of this situation). I'm trying really hard to use Azure SQL for its Always Encrypted with Secure enclaves capabilities in a solution I'm building, but it is getting harder and harder to justify. |
We are building a multi-phase plan for AE. Each phase corresponds to a complete set of functionality that can be released. |
I have an issue with updating an encrypted field.
For example:
My table
members
has an columndob
which is encryptedI can exec it in Azure studio, but cannot implement in code.
I always get
The encryption scheme for the columns/variables is (encryption_type = 'PLAINTEXT') and the expression near line '2' expects it to be DETERMINISTIC, or PLAINTEXT.
Thanks
The text was updated successfully, but these errors were encountered: