You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
The method
AbstractFBPreparedStatement.internalExecute(boolean)
will resetcurrentStatementResult
toStatementResult.NO_MORE_RESULTS
, whileFBStatement.internalExecute(String)
doesn't. The behaviour ofFBPreparedStatement
seems to be the right behaviour to me, butTestFBStatement.verifySingletonStatementWithException()
explicitly tests for this behaviour.Investigate the difference, and - if possible - ensure both behave the same.
The text was updated successfully, but these errors were encountered: