Capture SqlException Number #225
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
chlafreniere
requested review from
Charles-Gagnon,
MaddyDev and
lucyzhang929
as code owners
Charles-Gagnon
approved these changes
Apr 12, 2022
MaddyDev
approved these changes
Apr 12, 2022
Contributor
|
Merging this in to include in the new release. |
PBBlox
pushed a commit
to PBBlox/azure-functions-sql-extension
that referenced
this pull request
Apr 6, 2025
* First attempt SqlException Error Code * Capture SqlException.Number
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Extract SqlException number to help disambiguate SqlExceptions so that we can better fix customer issues with SqlClient.
I'm certainly unfamiliar here, so please feel free to take a hard look here. Should I still be adding the telemetry property if it's an empty string?