-
Notifications
You must be signed in to change notification settings - Fork 427
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
Fix | Fix for ResultSets being consumed when reading warnings #991
Conversation
Jars for testing: mssql-jdbc-PR991.zip |
Codecov Report
@@ Coverage Diff @@
## dev #991 +/- ##
==========================================
+ Coverage 50.09% 50.2% +0.1%
- Complexity 2878 2888 +10
==========================================
Files 120 120
Lines 27989 27996 +7
Branches 4677 4680 +3
==========================================
+ Hits 14022 14055 +33
+ Misses 11713 11686 -27
- Partials 2254 2255 +1
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.
I think testMultipleResultSets() should also test that the following is working (copied from getMoreResults() Javadoc:):
There are no more results when the following is true:
// stmt is a Statement object
((stmt.getMoreResults() == false) && (stmt.getUpdateCount() == -1))
Update the test with an update of any value (or no value) that returns an update count and do another select afterwards so that a ResultSet is expected after the update count.
I have verified that the jre8 version jar works in our test suite. |
Hi @biasb I've added the scenario as you mentioned, please let me know if I misunderstood anything. |
Fixes issue #969