fix SQLServerException wrapped by another SQLServerException#213
Merged
xiangyushawn merged 3 commits intomicrosoft:devfrom Mar 22, 2017
Merged
Conversation
…ther sql server exception
Codecov Report
@@ Coverage Diff @@
## dev #213 +/- ##
============================================
+ Coverage 32.82% 32.88% +0.06%
- Complexity 1436 1442 +6
============================================
Files 97 97
Lines 23383 23385 +2
Branches 3889 3889
============================================
+ Hits 7675 7691 +16
+ Misses 14163 14151 -12
+ Partials 1545 1543 -2
Continue to review full report at Codecov.
|
v-nisidh
approved these changes
Mar 21, 2017
| } | ||
| } | ||
| catch (SQLServerException e) { | ||
| throw e; |
Contributor
There was a problem hiding this comment.
Just add one line comment like SQLServerException should not again wrapped by SQLServerException
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
for issue #207