Replies: 1 comment
- 8000
-
|
I would lean towards option (1), Adding Command Timeout as a Parameter in Each SQL Wrapper Method. The reason for this choice is that this often needs to be customised on a per-query basis and a single value (from the connection string) for all queries isn't always appropriate. I would probably write it as |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I'm currently developing a tool called SQLWrapper, which aims to automatically generate a C# wrapper from SQL queries:
SQLWrapper NuGet Package
SQLWrapper GitHub Repository
Presently, the SQL wrapper does not include a command timeout feature.
I understand that there are scenarios where modifying the command timeout, especially for large queries, is necessary to increase query execution time.
I see two potential solutions to address this:
I'm seeking your feedback to determine which solution would be preferable: Solution 1 or 2?
Additionally, if you have the opportunity to test my SQLWrapper tool, I would greatly appreciate any feedback you can provide.
Beta Was this translation helpful? Give feedback.
All reactions