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

Investigate difference between FBStatement and FBPreparedStatement internalExecute #681

Closed
mrotteveel opened this issue Oct 18, 2021 · 1 comment

Comments

@mrotteveel
Copy link
Member

The method AbstractFBPreparedStatement.internalExecute(boolean) will reset currentStatementResult to StatementResult.NO_MORE_RESULTS, while FBStatement.internalExecute(String) doesn't. The behaviour of FBPreparedStatement seems to be the right behaviour to me, but TestFBStatement.verifySingletonStatementWithException() explicitly tests for this behaviour.

Investigate the difference, and - if possible - ensure both behave the same.

@mrotteveel
Copy link
Member Author

Conclusion stands, changed to set currentStatementResult to StatementResult.NO_MORE_RESULTS also for FBStatement (and FBCallableStatement) code paths. This means after an exception, retrieval of update counts (with Statement.getUpdateCounts()) will return -1 for all Statement implementations, not just FBPreparedStatement.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant