Work around issue with getIndexInfo() on SQL Server #7023
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
labkey-adam
requested review from
labkey-martyp,
labkey-matthewb and
labkey-tchad
Member
|
Verifying on TeamCity: https://teamcity.labkey.org/buildConfiguration/bt21/3657512 |
labkey-matthewb
approved these changes
Sep 8, 2025
labkey-tchad
approved these changes
Sep 9, 2025
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.
Rationale
After upgrading the Microsoft SQL Server JDBC driver to 13.2.0.jre11, various tests starting failing because its new
getIndexInfo()implementation returns a ResultSet that throws ifnext()is called after the results have been exhausted. More details: https://www.labkey.org/home/Developer/issues/issues-details.view?issueId=53885Related Pull Requests
Tasks 📍
Manual Testing / Verify Fix