test: Add failing test producing NPE with Statement.closeOnCompletion()#1518
Closed
sehrope wants to merge 1 commit intomicrosoft:devfrom
Closed
test: Add failing test producing NPE with Statement.closeOnCompletion()#1518sehrope wants to merge 1 commit intomicrosoft:devfrom
sehrope wants to merge 1 commit intomicrosoft:devfrom
Conversation
Adds a failing test that produces an NPE when a Statement is marked closeOnCompletion() and then used more than once to execute a query via Statement.executeQuery(...).
Contributor
|
close replaced by #1639 |
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
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.
The driver produces an NPE if a Statement enables
closeOnCompletion()and is then used to execute more than one command viaStatement.executeQuery(...). It should be throwing a more specific SQLException.Sample code to produce the NPE:
Ran into this while looking at a change the Postgres driver and wanted to see how other drivers handle this situation. See here for more details: pgjdbc/pgjdbc#1905 (comment)
Here's the stack trace:
Note this PR doesn't fix anything. I just added the failing test to reproduce the error.