Skip to content
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

#2299: added missing null check of e.getCause(). #2300

Merged
merged 1 commit into from
Jan 15, 2024
Merged

#2299: added missing null check of e.getCause(). #2300

merged 1 commit into from
Jan 15, 2024

Conversation

jesperah
Copy link
Contributor

if the caught exception does not have a cause then pass the caught exception as the cause to the SQLTimeoutException instead of the null "e.getCause()". (#2299)

if the caught exception does not have a cause then pass the caught exception as the cause to the SQLTimeoutException instead of the null "e.getCause()". (#2299)
@lilgreenbird lilgreenbird added this to In progress in MSSQL JDBC via automation Jan 15, 2024
@lilgreenbird lilgreenbird added this to the 12.6.0 milestone Jan 15, 2024
@lilgreenbird lilgreenbird moved this from In progress to Under Peer Review in MSSQL JDBC Jan 15, 2024
@lilgreenbird lilgreenbird merged commit 0f04ce6 into microsoft:main Jan 15, 2024
17 checks passed
MSSQL JDBC automation moved this from Under Peer Review to Closed/Merged PRs Jan 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
MSSQL JDBC
  
Closed/Merged PRs
Development

Successfully merging this pull request may close these issues.

SQLServerStatement#executeCommand missing null check on SQLServerException#getCause.
4 participants