Fix | Fix for ResultSets being consumed when reading warnings#991
Fix | Fix for ResultSets being consumed when reading warnings#991cheenamalhotra merged 8 commits intomicrosoft:devfrom
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.
|
biasb
left a comment
There was a problem hiding this comment.
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