-
Notifications
You must be signed in to change notification settings - Fork 426
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Improvement | Added new APIs to retrieve SQL Server error information received with SQLServerException #905
Conversation
… received with SQLServerException
Codecov Report
@@ Coverage Diff @@
## dev #905 +/- ##
============================================
- Coverage 48.79% 48.71% -0.09%
+ Complexity 2824 2821 -3
============================================
Files 118 118
Lines 27877 27882 +5
Branches 4642 4642
============================================
- Hits 13602 13582 -20
- Misses 12086 12103 +17
- Partials 2189 2197 +8
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why are we renaming StreamError to SQLServerError? StreamError is a child of the StreamPacket and all the children of StreamPacket have the same naming scheme, and only StreamError is being changed to SQLServerError?
Please add tests for the new APIs. |
src/main/java/com/microsoft/sqlserver/jdbc/SQLServerException.java
Outdated
Show resolved
Hide resolved
f2645ca
Fixes issue #885
Currently driver does not provide access to detailed information about SQLServerException when error is raised from SQL Server. This PR renames class StreamError to SQLServerError and provides public APIs that can be called to read additional SQL Server error information.
New Public APIs Added: