From 8c80632aea2b29ebf94a439279eebb14efab2490 Mon Sep 17 00:00:00 2001 From: davidshi Date: Fri, 1 Mar 2024 16:23:26 -0600 Subject: [PATCH] update readme --- README.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/README.md b/README.md index e254b6b0..5e98abe1 100644 --- a/README.md +++ b/README.md @@ -427,9 +427,8 @@ If the correct key provider is included in your application, decryption of encry Encryption of parameters passed to `Exec` and `Query` variants requires an extra round trip per query to fetch the encryption metadata. If the error returned by a query attempt indicates a type mismatch between the parameter and the destination table, most likely your input type is not a strict match for the SQL Server data type of the destination. You may be using a Go `string` when you need to use one of the driver-specific aliases like `VarChar` or `NVarCharMax`. -*** NOTE *** - Currently `char` and `varchar` types do not include a collation parameter component so can't be used for inserting encrypted values. Also, using a nullable sql package type like `sql.NullableInt32` to pass a `NULL` value for an encrypted column will not work unless the encrypted column type is `nvarchar`. +*** NOTE *** - Currently `char` and `varchar` types do not include a collation parameter component so can't be used for inserting encrypted values. https://github.com/microsoft/go-mssqldb/issues/129 -https://github.com/microsoft/go-mssqldb/issues/130 ### Local certificate AE key provider