FIX: Timeout during cursor creation and not execute #348
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Work Item / Issue Reference
Summary
This pull request refactors how query timeouts are set for statement handles in the
mssql_python/cursor.pymodule. The main improvement is moving the logic for setting the query timeout from theexecutemethod to the cursor initialization process, ensuring the timeout is consistently applied whenever the statement handle is allocated or reset.Statement handle timeout management:
_set_timeoutmethod to set the query timeout attribute on the statement handle during cursor initialization, following best practices for performance. (mssql_python/cursor.py)executemethod, centralizing timeout management in the cursor lifecycle. (mssql_python/cursor.py)