QueryAsync hangs with Column Encryption Setting in MSSQL CN string
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 18.4k
- Forks
- 3.7k
- Avg merge
- 5h 8m
- Merged PRs (30d)
- 1
Description
Dapper 2.0.35
Core 3.1
MSSQL 14.0.3294.2
If we call QueryAsync<> on a Stored Proc, with at least 1 parameter and with Column Encryption Setting=Enabled in the cn string, and that proc throws an exception, a subsequent call to that proc will hang in QueryAsync<>.
Column Encryption Setting=Disabled or using Query<> eliminates the issue. The issue doesn't happen with Microsoft.Data ExecuteReaderAsync.
Program.cs.txt.
GetBadThing.sql.txt
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the behavior from the attached Program.cs.txt and GetBadThing.sql.txt using Dapper 2.0.35, .NET Core 3.1, and SQL Server. Compare QueryAsync with Query and Microsoft.Data ExecuteReaderAsync under the stated connection settings; done means the subsequent stored-procedure call no longer hangs after the first call throws.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, sql
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100